1996-10-15 - using TCP sequence numbers for stego

Header Data

From: “Mark M.” <markm@voicenet.com>
To: cypherpunks@toad.com
Message Hash: 999f9263f0239021c3c82acf93899a2a27eccc9be3c3f5db29fbf1aaa1d0dea7
Message ID: <Pine.LNX.3.95.961015165112.590A-100000@gak.voicenet.com>
Reply To: N/A
UTC Datetime: 1996-10-15 21:08:21 UTC
Raw Date: Tue, 15 Oct 1996 14:08:21 -0700 (PDT)

Raw message

From: "Mark M." <markm@voicenet.com>
Date: Tue, 15 Oct 1996 14:08:21 -0700 (PDT)
To: cypherpunks@toad.com
Subject: using TCP sequence numbers for stego
Message-ID: <Pine.LNX.3.95.961015165112.590A-100000@gak.voicenet.com>
MIME-Version: 1.0
Content-Type: text/plain


-----BEGIN PGP SIGNED MESSAGE-----

Would using TCP sequence numbers to carry stegoed data be practical?  The data
would have to be removed at a lower level.  This would mean kernel patches and
extra system calls in UNIX.  I have no idea what this would require under
Windows or Mac.  This seems like the ideal place to stego data because
most OS's have started using random sequence numbers.  Any ideas?

Mark
- -- 
finger -l for PGP key
PGP encrypted mail prefered.

-----BEGIN PGP SIGNATURE-----
Version: 2.6.3
Charset: noconv

iQEVAwUBMmP7sSzIPc7jvyFpAQHlUQf+JwmltREsYq65f5YPOdubmr8hxAjfiOa+
zIX7VpP75qm+SgiZTxBaioN2pVzW0yCb36IqNKYuZuUww/ip8Bh/0aNnyzNguD+p
jXVOLpzbfBeD33Q+NLag6N2R2PogZQT2yx2vfSwQ9zeyoZ1CYTxiKZHDq06czzAt
gq3wszp0l9U1jr2xTnmprNYofYUrvWitpId41tTbyx336dmJ5lNKS1Nssu/+vCZC
B9Gib+s/ayQz6BGuEDCVqr36cZY75uHYfUuMnIHnONYAsFC4qR1vNdJ/OnCXJJR2
D6Ns9POsb9NGCh0pFzGjDavpQKwIU9b/Br30vge1tKsPA30GByPJMQ==
=NaaI
-----END PGP SIGNATURE-----






Thread