On 2004-12-20 at 14:56:49 JakeLM wrote:

> I have send my public key to those servers:
> hkp://keyserver.kjsl.com
> hkp://pks.gpg.cz
> ldap://horowitz.surfnet.nl:11370
> hkp://blackhole.pca.dfn.de .

You only have to send your public key to the nearest server in the key
server network.  These servers regularly synchronize, but it takes
some time.  So please don't expect your key to turn up in 0.001 ms! :)

Anyway, it seems to be okay now:

gpg: Signature made 12/20/04 14:56:28 W. Europe Standard Time using DSA key ID 
840D7D5C
gpg: requesting key 840D7D5C from ldap server horowitz.surfnet.nl
gpg: key 840D7D5C: public key "JakeLM <[EMAIL PROTECTED]>" imported
gpg: Total number processed: 1
gpg:               imported: 1
gpg: Good signature from "JakeLM <[EMAIL PROTECTED]>"
gpg: WARNING: This key is not certified with a trusted signature!
gpg:          There is no indication that the signature belongs to the owner.
Primary key fingerprint: 9D21 E846 EB39 709A 47FA  728E 35FD C24C 840D 7D5C


> And wich way is better:
> signing the mail with MIME (like yours) or in the mail text like this message 
> ?

This depends.  I prefer MIME, since it doesn't "screw up" the
plaintext message.  However, some people with braindead email clients
*cough* Outlook *cough* will have problems reading your mail, since
they display both the inline plain text part and the signature part as
scary "attachments", without any extension!  These "attachments" might
even be blocked by even more braindead mail gateways and/or
administrators.

(Note to The Bat developers: can you PLEASE add Content-Disposition
MIME headers for GPG/PGP signed messages!  Thanks!)

OTOH, if you use inline signatures, as you've done just now, your mail
will generally be readable by everyone.  But you're certain to get
questions about "weird techno-garbage headers" in your mail from
non-technical human users.  Also, the process makes some small changes
to your plaintext, such as replacing "-" at the beginning of a line
with "- -", and possibly wrapping your text.

A bigger problem is that plaintext is bound to be screwed up by a lot
of mail software, causing your signature to become invalid!


> To write the personal fingerprint somewhere in the mail is a good idea
> and it's useful ?

You can do this if you like, but it doesn't win you much.  If The Evil
Guys/Gals(TM) can forge your mail, then they can probably also forge
the fingerprint in them. :)  Just try to get as many good signatures
as possible on your public key.
 

Attachment: pgpRUH24xkJ5k.pgp
Description: PGP signature

________________________________________________________
 Current beta is 3.0.2.10 | 'Using TBBETA' information:
http://www.silverstones.com/thebat/TBUDLInfo.html
IMPORTANT: To register as a Beta tester, use this link first -
http://www.ritlabs.com/en/partners/testers/

Reply via email to