[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
-----BEGIN PGP SIGNED MESSAGE-----
In message <[email protected]> you write:
>But (except for monitoring messages going into and out of the remailer,
>or operator logging) how is anyone to know which remailers were involved
>in a chain? Isn't this one of the things that chaining is supposed to
>prevent?
That is exactly what chaining is supposed to prevent.
>A more accurate objection might be that if spam/proprietary data is
>chained through remailers, then EVERY remailer is at risk.
This is more correct than my previous statement. ALL remailers would be
at risk.
>BTW, I think your safeguards (which I am _not_ objecting to) only make
>it a little bit harder to use your remailer to post stolen code or
>whatever. Someone could easily break the posts up into pieces and
>chain them through your remailer, perhaps through different chains as
>well, e.g.:
I agree that it only makes it a little harder. I never meant it as a
preventative and it never will be. But if the remailer is going to be
used to send out large amounts of data, i.e. source code and spam, I
wanted to increase the level of difficulty on the part of the individual
committing the act.
>Or are you going to block posts from remailers that forward spam to you?
>(A cure worse than the disease, IMHO).
I have no intention of blocking the other remailers.
John A. Perry - KG5RG - [email protected]
WWW - http://jpunix.com
PGP 2.62 key for [email protected] is on the keyservers.
PGP-encrypted e-mail welcome!
Finger [email protected] for PGP keyserver help.
Finger [email protected] for remailer help.
-----BEGIN PGP SIGNATURE-----
Version: 2.6.2
Comment: Finger [email protected] for PGP keyserver help.
iQCVAwUBLsyCVlOTpEThrthvAQGkJgP/QB/4Bi07Xyfc6xcU/Ua88XwUW7Gdx0BE
n2rraXqV9qO5vx6HaGh9n0dLZXqh2J+ElAbBxKnNQ7bkh6KwnEGXkLLdKVitXrDI
073iZrvfcFSzKl9PC+p36qjwuGMFJadmP5piBpSQ1fQLY/rYUJzyrUME8277b2NM
4HxW0BBEjGY=
=QZyL
-----END PGP SIGNATURE-----