[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

RE: A problem with identification


I found in db.debian.org...

ub  1024D/89B2B733 2000-06-19 Per Lundberg <plundis@chaosdev.org>
     Key fingerprint = 67FE A7C9 C8A9 9BDF B8DF  6224 973C 47BE 89B2 B733
sig        89B2B733 2000-06-19  Per Lundberg <plundis@chaosdev.org>
sig        90CB3189 2000-06-19  Per Lundberg <plundis@debian.org>
sub  1024g/901C7398 2000-06-19
sig        89B2B733 2000-06-19  Per Lundberg <plundis@chaosdev.org>

Is this not the key Per used?

Any-hoo...you can do the New Maintainer steps asynchronously, they
dont really have to be performed in order.  Perhaps if Per has a 
new key, by the time you get the other steps complete, his key
will be updated in the keyring.

My 2 cents...

Jim Westveer <jwest@debian.org>


On 17-Sep-2000 Christian Surchi wrote:
> Hi,
> I'm processing my first NM and I'm in identification process. He is Tom
> Cato Amundsen <tomcato@iname.com>. He has a gpg key signed by Per
> Lundberg <plundis@debian.org>, but Per signed Tom's key with his new gpg
> key, and this key is not in keyring yet. I could only get that key from
> another keyserver, but it has neither a d.o id. How should I behave?
> Should I wait for that key in keyring or can I skip this step and work
> with Tom on following steps?
> Thanks in advance,
> Christian
> -- 
> Christian Surchi   |   csurchi@debian.org   |   christian@firenze.linux.it   

"Bother," said Pooh as he struggled with sendmail.cf.
"It never does quite what I want."
"I wish Christopher Robin were here.". 
E-Mail: jwest@lcs.issaquah.wa.us      jwest@debian.org
work :  425-591-3002                  Date: 17-Sep-2000
home    425-392-0141                  Time: 14:46:49
pgp-key 0x36129171                    gpg-key 0x9823336C  

Reply to: