Exposing email addresses on key servers

[Philipp Schafft]

reflum,

On Sun, 2009-06-28 at 13:20 +0800, Jesse Cheung wrote:
> >  You can also use a freeform UID, which contains name and comment,
> but
> > leave the email field empty.
> Yeah I found it a good idea! BTW it seems the file format doesn't
> really stop us from putting invalid email address in the UID, so is
> there a switch in gpg/gpg2 command line that skips email address
> format checking altogether? My intension is to put obscured email
> addresses, like rot13(xxx) or reversed(at-dot(email)) kind of stuff in
> that field. Seahorse can do that, but only when generating keys, not
> adding new UIDs 

I often use mail addresses containing a '=' or use UUCP style addresses
(host!user). They are perfectly valid just not commonly used and
spambots don't find them.

-- 
Philipp.
 (Rah of PH2)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 482 bytes
Desc: This is a digitally signed message part
URL: </pipermail/attachments/20090629/999b0a99/attachment.pgp>