-----BEGIN PGP SIGNED MESSAGE-----
With the additional nym servers coming on the scene comes the question of whether or not to "claim" our alpha.c2 nym on the other ones, too. E.g., if we are foobar@alpha.c2.org, should we also become foobar@nym.gondolin.org and foobar@nym.alias.net, too?
*shrug* sounds good
an oversimplified scenario would be if an attacker sends a message to all three nyms, then watches three PGP conventionally encrypted messages arrive in our mailbox.)
A "safer" way would be to have the other two nyms have a fake address, but then we couldn't receive mail with it. A trickier way would be to have the reply block point to alt.anonymous, but then we'd
Traffic analysis can happen even with only one address. (just spam attack the one, or whatever) You can protect yourself somewhat by putting lots of latency into your reply block, including random. You could have one nym point to another. ObMindWandering Since expiration dates were "supposed" to be added to type I, and there's at least some spam-detection code, why not add "Hi, I'm reply block #XYZ. Watch for spam attacks from me." warnings inside the reply block. (To be lost on the next hop, of course) If good spam-detection code ever catches on in type I, it would be nice to be able to trigger it yourself. ObSnakeOil: Post your source code or go away, you're wasting bandwidth. ObNoiseInGeneral: skipping it in leaps and bounds. MUCH quieter. =) - -- <don@cs.byu.edu> fRee cRyPTo! jOin the hUnt or BE tHe PrEY PGP key - http://students.cs.byu.edu/~don or PubKey servers (0x994b8f39) June 7&14, 1995: 1st amendment repealed. Junk mail to root@fryser.dk.net * This user insured by the Smith, Wesson, & Zimmermann insurance company * -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQB1AwUBMSmE/cLa+QKZS485AQHbigL+Ja1krN2TUFyR+aFR6C0wI5zj4160Iz0q 0tLKSA7X+px+lUwCLdRuEk4wskcNhXFP5ESpCxpQKw2CZRjNlJ4vZA54wE9PBlxf ibR4ZpktxfFsYr+rkdwt0JWUj/+65d6P =Pwji -----END PGP SIGNATURE-----