trunk/caff/README.v3-keys

v3 keys are evil
----------------

The good thing about v4 keys is that the fingerprint ends contains the 8 byte
(16 char) key id at the and and that the 8 byte key id likewise ends in the 4
byte key id. For v3 keys it does not. This, and some issues with HKP key
servers make the handling of v3 a PITA.

To sign v3 keys with caff, do the following:

$ caff <keyid>

[note that caff does not accept fingerprints for v3 keys, use keyids]

The key will be imported from the keyserver, but caff thinks it failed. Now run
caff again with -R:

$ caff -R <keyid>

Since the key is already there, caff will proceed.


Of course, this could be automated... patches welcome :)

 -- Christoph Berg <cb@df7cb.de>  Sat,  2 Jul 2005 21:34:48 +0200

1	v3 keys are evil
2	----------------
3
4	The good thing about v4 keys is that the fingerprint ends contains the 8 byte
5	(16 char) key id at the and and that the 8 byte key id likewise ends in the 4
6	byte key id. For v3 keys it does not. This, and some issues with HKP key
7	servers make the handling of v3 a PITA.
8
9	To sign v3 keys with caff, do the following:
10
11	$ caff <keyid>
12
13	[note that caff does not accept fingerprints for v3 keys, use keyids]
14
15	The key will be imported from the keyserver, but caff thinks it failed. Now run
16	caff again with -R:
17
18	$ caff -R <keyid>
19
20	Since the key is already there, caff will proceed.
21
22
23	Of course, this could be automated... patches welcome :)
24
25	-- Christoph Berg <cb@df7cb.de> Sat, 2 Jul 2005 21:34:48 +0200
26