Key consistency checks

This requirement has been approved by Jonathan McDowell <noodles@earth.li> 4 years, 6 months ago.

This process has been closed by noodles on 2020-09-14: no further modifications are possible.

Potential problems

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

OpenPGP fingerprint	7317 3B09 3B03 CFB8 5108 AD14 B11B D919 079A 3B98
Main key	ok (last updated: 2025-03-05 17:36 UTC)
UID Joe Nahmias (Debian Packaging) <jello, debian.org>	ok, 3 non-DD sigs, 1 DD sigs: F6D3495BB0AE9A02: Clint Adams <clint@debian.org>
UID Joseph Nahmias <joe, nahmias.net>	ok, 3 non-DD sigs, 0 DD sigs: none

Active key endorsements

Endorsed by	Date	Statement	Actions

Log

Date	Author	Action	Content	Public
2020-09-06 18:12	noodles	req_approve	I think this is fine; key is in emeritus and when originally added to the active keyring (f6fd814ec0a927cd1220e32e246468be2b3dae38) was signed by clint, dkg + micah. dkg + micah have rotated their keys which is why only clint's signature is currently valid. I strongly recommend Joseph gets some more cross signatures with DDs arranged, but don't believe it's a blocker for readding his key.	yes