I continue with that problem. Tom's key is signed by a new key of Per Lundberg as I can see:
bash-2.03$ gpg --check-sigs tomcato pub 1024D/A5E43EA3 1999-12-18 Tom Cato Amundsen <[EMAIL PROTECTED]> sig! A5E43EA3 1999-12-18 Tom Cato Amundsen <[EMAIL PROTECTED]> sig! BDFAA963 2000-08-23 Per Lundberg <[EMAIL PROTECTED]> uid Tom Cato Amundsen <[EMAIL PROTECTED]> sig! A5E43EA3 2000-08-04 Tom Cato Amundsen <[EMAIL PROTECTED]> sub 1024g/9284413D 1999-12-18 sig! A5E43EA3 1999-12-18 Tom Cato Amundsen <[EMAIL PROTECTED]> Key that Per used to sign it is this: bash-2.03$ gpg --check-sigs BDFAA963 pub 1024D/BDFAA963 2000-08-17 Per Lundberg <[EMAIL PROTECTED]> sig! 6394265E 2000-08-22 peter karlsson (Fidonet#2:210/45.0) <[EMAIL PROTECTED]> sig! BDFAA963 2000-08-17 Per Lundberg <[EMAIL PROTECTED]> sub 1024g/CE7BD79A 2000-08-17 sig! BDFAA963 2000-08-17 Per Lundberg <[EMAIL PROTECTED]> This key is not in keyring and it's not signed with an old key from Per, but only by another developer key. How can I behave? Should I wait for Per's new key in keyring or should I consider the relationship Peter Karlsson -> Per Lundberg -> Tom Cato Amundsen as good? TIA Christian -- Christian Surchi | [EMAIL PROTECTED] | [EMAIL PROTECTED] FLUG: http://www.firenze.linux.it | Debian GNU/Linux: http://www.debian.org -----------------> http://www.firenze.linux.it/~csurchi <------------------ If you stand on your head, you will get footprints in your hair.
