John Gilmore writes:
My favorite scheme was to encode messages in trailing spaces and/or tabs in netnews messages. You could also put internal tabs in place of spaces. and other fun things...
In fact, you could do this with news messages that flow "through" your site, (if the messages aren't protected with a crypto checksum), so that you would not be the message's sender (and it wouldn't be addressed to anyone either -- recipients get very good privacy).
Hmmm... While this certainly does provide some privacy, it also can break things, which is not nice to do to other people's messages. For example, if other people are encoding messages in trailing spaces or tabs in netnews messages, you'll replace their hidden messages with your own :-) I don't know if there's much news out there with Content-Length: headers or other byte-counting headers that would be disrupted; Lines: is obviously not bothered. On the other hand, if the messages that appear to be flowing through your site are really being generated there, either as forgeries of messages from other people, or forgeries of messages from anonymous posting sites, or are forged messages you're really posting through an anonymous posting site, you gain about the same effect (assuming your forgery is good enough to not attract attention.) (Forging messages from other people is best done either with cooperative people, or fake people, or people who don't mind like MAILER-DAEMON%Fidogate@BAR.BiTNet.) Bill Stewart
participants (1)
-
wcs@anchor.ho.att.com