1996-03-12 - Re: PGP reveals the key ID of the recipient of encrypted msg

Header Data

From: Gary Howland <gary@kampai.euronet.nl>
To: cypherpunks@toad.com
Message Hash: 0c40b1117893a922b4a32618d851a2fa69e9533e81dd12ad42e7a2dbe9686030
Message ID: <199603121020.FAA20726@bb.hks.net>
Reply To: N/A
UTC Datetime: 1996-03-12 19:42:59 UTC
Raw Date: Wed, 13 Mar 1996 03:42:59 +0800

Raw message

From: Gary Howland <gary@kampai.euronet.nl>
Date: Wed, 13 Mar 1996 03:42:59 +0800
To: cypherpunks@toad.com
Subject: Re: PGP reveals the key ID of the recipient of encrypted msg
Message-ID: <199603121020.FAA20726@bb.hks.net>
MIME-Version: 1.0
Content-Type: text/plain


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

markm@voicenet.com wrote:
On Mon, 11 Mar 1996 savron@world-net.sct.fr wrote:

> > I began testing PGP  a few days ago ( I'm a PGP newbie ) and I found
> > that it gives out the key ID of an encrypted message . From this you
> > can get the  identification of the recipient of the message , if it's
> > someone who has publicaly  distributed his  key (keyserver , homepage
> > ...) . So even if you are unable to decode the message you  can find
> > who is the recipient of a given message . I think this is a big
> > privacy problem .
> 
> The recipient of the message is right in the "To:" header of the message.
> If you anonymously remail a message, however, only the last remailer in the
> chain will know to whom the message is encrypted, but the last remailer can
> also just read the "To:" header.  I don't find this to be a problem at all.

Not everything goes via email, eg. mail exchanges via alt.anonymous.

Gary
- --
pub  1024/C001D00D 1996/01/22  Gary Howland <gary@kampai.euronet.nl>
Key fingerprint =  0C FB 60 61 4D 3B 24 7D  1C 89 1D BE 1F EE 09 06 

- ---
[This message has been signed by an auto-signing service.  A valid signature
means only that it has been received at the address corresponding to the
signature and forwarded.]

-----BEGIN PGP SIGNATURE-----
Version: 2.6.2
Comment: Gratis auto-signing service

iQBFAwUBMUVP2CoZzwIn1bdtAQGlBwF8DxnCbaU1P0pz0TQ7OkuE9kkuSgnf6Ump
3p6Ut328gqJGj7oEza5S78rjBMpHgUej
=2Ymx
-----END PGP SIGNATURE-----





Thread