Re: Raphael Hertzog 2007-07-17 <[🔎] 20070716231725.GC29703@ouaza.com> > > id | uid | name > > ------+----------------+--------------------------------- > > 1319 | thijs | Thijs Kinkhorst > > > > id | fingerprint | uid > > ------+------------------------------------------+------ > > 5823 | F7867D1E8EEB8DE7EBBE05BF25D28CC5957D58CF | 1319 > > 5900 | 86CB46D209591D06AE9C2A666CF485B3DCBA43DF | > > > > You will have to wait for (or poke) the ftp-masters to do a "dak > > import-ldap-fingerprints" run. > > Is this true? Fingerprints of subkeys are never imported in the LDAP. > In userdir-ldap at least, authentication with subkeys is always first > resolved to the main key with the the help of the keyring and then the > fingerprint of the main key is looked for in the LDAP database. > > Maybe you could do something similar. You need a recent copy of the > keyring (that you can get by public rsync on keyring.debian.org). I don't know how that's handled in LDAP, but the above is what the projectb knows about that keyid. The uid column will have to be filled for ddpo to be able to know that "86CB46D209591D06AE9C2A666CF485B3DCBA43DF" is actually "thijs". You can try reopening the bug and reassigning it to ftp.debian.org if there is a general problem with subkeys and the problen doesn't resolve itself with then next import-ldap-fingerprints run (which happens every few weeks). PS 1: I know that the mail gateway at change@db.d.o does not support subkeys, but dak apparently does. PS 2: Note that the projectb doesn't correlate a (source) packages's maintainer and the uid/key used to sign it in any way, that's two different text fields. Christoph
Attachment:
signature.asc
Description: Digital signature