Re: Key Server Information for gpg

Andrei Smirnov wrote:
>>http://morlug.org/meetings/
>
> David Sith's instructions point to the command:
>
> gpg --keyserver wwwkeys.us.php.net --send-keys You Key ID
>
> My question is what should I place instead of "You Key ID" above?
> Is it the string appearing after "Key fingerprint =" in the output
> from
>
> gpg --fingerprint username

I observe what the problem is in the paper titled "What to do at home?"
   The paragraph under the title "Key ID" goes into more detail about
one of the most accurate ways of finding a particular key which is the
use last 8 hexadecimal characters of a fingerprint.  I inserted a 2
after E651(2) 1C7E .. actual Key ID should be E651 1C7E and used as
E6511C7E .  I'll upload the corrected version.

So for instance ..

gpg --fingerprint smirnov
pub  1024D/F5A073F4 2002-11-12 Andrei Smirnov (Computational Mechanics)
<[email protected]>
      Key fingerprint = EF7A 9284 FAB2 BF80 ABF2  C456 6814 4991 F5A0 73F4
sub  1024g/3115439E 2002-11-12

so for ..

F7A 9284 FAB2 BF80 ABF2 C456 6814 4991 F5A0 73F4

You would use F5A073F4 as the short-hand Key ID.

However, it isn't strictly necessary to find a key in this manner.
man(1) gpg it goes into more detail:

How to specify a user ID
------------------------

There  are  different ways to specify a user ID to GnuPG; here are some
examples:

234567C4

0F34E556E

01347A56A

0xAB123456
    Here the key ID is given in the usual short form.

234AABBCC34567C4

0F323456784E56EAB

01AB3FED1347A5612

0x234AABBCC34567C4
    Here the key ID is given in the long form as used by  OpenPGP
(you can get the long key ID using the option --with-colons).

1234343434343434C434343434343434

123434343434343C3434343434343734349A3434

0E12343434343434343434EAB3484343434343434

0xE12343434343434343434EAB3484343434343434
    The best way to specify a key ID is by using the  fingerprint of
the  key.  This avoids any ambiguities in case that there are duplicated
key IDs (which are really rare  for  the  long key IDs).

=Heinrich Heine <[email protected]>
    Using  an  exact  to  match string.  The equal sign indicates this.

<[email protected]>
    Using the email address part which must  match  exactly.  The
      left angle bracket indicates this email address mode.

+Heinrich Heine duesseldorf
    All  words  must  match  exactly (not case sensitive) but can appear
in any order in the user ID.  Words are any  sequences of  letters,
digits,  the underscore and all characters with bit 7 set.

Heine

*Heine
    By case insensitive substring matching.  This is the  defaul mode
but applications may want to explicitly indicate this by putting the
asterisk in front.

Note that you can append an exclamation mark (!) to key IDs or
finger­prints.  This flag tells GnuPG to use exactly the given primary
or sec­ondary key and not to try to figure out which secondary or
primary key to use.

Hope that helps,


Jonathan


> or something else?
>
> Andrei

_______________________________________________
Morlug mailing list
[email protected]
http://mailman.morlug.org/mailman/listinfo/morlug

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFCJRZWF+LALi2rcDcRAmFzAJ0RkQ+g9/lB3ISXhfVNsf/1rNtKkwCfUb2P
a4yiAk8LhkB+MKPkMU/HQxs=
=YeYz
-----END PGP SIGNATURE-----