On Mon, Aug 28, 2000 at 04:38:16PM -0500, Signal 11 wrote: > > with a random port (they can just detect that you are making an > > encrypted channel - if they detect lots of encrypted channels, > > especially ones coming in from outside, they will be tipped off). > > Haven't used a packet sniffer, have you? They decrypt protocols, > match up to filters and stuff. You can't just point to a binary > stream and go "oooh - encrypted!" A packet sniffer requires a > protocol definition, how to interpret the data. How can you tell > the difference between ftp-data stream of a jpeg file and freenet > traffic (assuming, of course, you weren't watching the control > traffic)?
Unless there is no indicator of the protocol and version before an encrypted session is set up, they will be able to easily see this. Therefore, we should make the actual protocol in use declared *after* the encrypted session is started. There should be no indications of what protocol is in use before encryption is started. -- Travis Bemann Sendmail is still screwed up on my box. My email address is really bemann at execpc.com. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 1276 bytes Desc: not available URL: <https://emu.freenetproject.org/pipermail/devl/attachments/20000828/5780ea62/attachment.pgp>
