Key consistency checks
This requirement looks incomplete.
- no UID found that fully satisfies requirements
Every Debian member needs a GPG key of sufficient strength. In addition, all keys should be certified
so we can link them to a real-world identity.
The normal requirements are:
- the key should be type RSA and version 4 or greater
- the key should have the sign, certify and encrypt capabilities (subkeys are encouraged)
- the primary cryptographic material should be at least 4096 bits
- the UIDs used by an applicant to work in the project should be signed by at least two existing Debian members (1 for DM applications)
- as an alternative to the previous requirement, the key can be endorsed (see link at the bottom of the page) by multiple Debian Members (the number of required endorsements depends on the endorsement's age and nature)
- pseudonyms or anonymity are acceptable in certain circumstances
If the key does not meet these requirements, and you would struggle to create one which does, contact Front Desk.
Keys are first searched in
hkps://keyring.debian.org. If no key is found,
then the key will be imported from
hkps://keyserver.ubuntu.com/. Please ensure that you
have sent your key to Ubuntu's key server. Sending public keys to keyring.debian.org will only work if your
key is already in Debian's keyring and will only be taken into account after the Keyring Maintainers
updated it. For Debian Maintainers and Developers, please remember to send your key to both servers.
This check will be approved manually by Front Desk as the application progresses.
Key check results
|DB52 7D8E D64B DBB7 BA48 ECD0 3357 018E B999 9C0A
ok (last updated: 2024-02-16 17:34 UTC)
|UID Fabian Gruenbichler <debian, fabian.gruenbichler.email>
ok, 0 non-DD sigs,
1 DD sigs:
- CB06EA7B78DBE151: Birger Schacht <email@example.com>
Active key endorsements
|Ok, I'll wait for this update to go on, but in the meantime I'll assign you an AM.
|yes - https://keyserver.ubuntu.com/pks/lookup?search=debian%40fabian.gruenbichler.email&fingerprint=on&op=index
but AFAIU, that has no effect since my key (by virtue of being a DM) is already in the debian keyring. evidently today's update didn't pick it up, so I just re-sent the key to hkp://keyring.debian.org hoping that the Februrary update will contain it..
Did you also send the updated key on keyserver.ubuntu.com ?
|my key already got a second signature, it's just not yet visible in the "live" Debian keyring AFAICT (because I sent it to the keyservers after the last Debian keyring update). the next sync should take care of that I hope - if not, I'll take a closer look!
|Hello Fabian, and thanks for applying to become DD. You'd need, at least, two key signatures and or strong-enough key endorsements. Do you have any plan for that?