Key consistency checks

This requirement has been approved by Jonathan McDowell <noodles@earth.li> 8 years ago.

This process has been closed by nm@debian.org on 2017-05-07: no further modifications are possible.

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	7D6A DB75 0F91 0855 8948 4BE6 77C0 C75E 7B65 0808
Main key	ok (last updated: 2025-04-25 20:34 UTC)
UID James Valleroy <jvalleroy, mailbox.org>	ok, 6 non-DD sigs, first 10 of 20 DD sigs: A1489FE2AB99A21A: Dirk Eddelbuettel <edd@debian.org> 2C7C3146C1A00121: Jonas Smedegaard <dr@jones.dk> 357312559D1E064B: Ondřej Nový <novy@ondrej.org> 39278DA8109E6244: Guilhem Moulin 5556A34E04A3610B: Sascha Steinbiss <satta@tetrinetsucht.de> 5A8830475F7D1061: Nicholas D Steeves <nsteeves@gmail.com> CC65B0CDEC275D5B: ChangZhuo Chen (陳昌倬) <czchen@czchen.org> DA82830E3CCC3A3A: Alexandre Viau <alexandre@alexandreviau.net> F5C83C05D9CEEEEE: Chris Boot <bootc@boo.tc> 664F1238AA8F138A: Daniel Lange <DLange@debian.org>
UID James Valleroy <jvalleroy, freedombox.org>	ok, 5 non-DD sigs, first 10 of 21 DD sigs: A1489FE2AB99A21A: Dirk Eddelbuettel <edd@debian.org> 2C7C3146C1A00121: Jonas Smedegaard <dr@jones.dk> 357312559D1E064B: Ondřej Nový <novy@ondrej.org> 39278DA8109E6244: Guilhem Moulin 5556A34E04A3610B: Sascha Steinbiss <satta@tetrinetsucht.de> 5A8830475F7D1061: Nicholas D Steeves <nsteeves@gmail.com> CC65B0CDEC275D5B: ChangZhuo Chen (陳昌倬) <czchen@czchen.org> DA82830E3CCC3A3A: Alexandre Viau <alexandre@alexandreviau.net> F5C83C05D9CEEEEE: Chris Boot <bootc@boo.tc> 664F1238AA8F138A: Daniel Lange <DLange@debian.org>
UID James Valleroy <jvalleroy, debian.org>	ok, 1 non-DD sigs, 0 DD sigs: none

Active key endorsements

Endorsed by	Date	Statement	Actions

Log

Date	Author	Action	Content	Public
2017-04-25 18:16	noodles	req_approve	At least 2 signatures is strongly preferred, and you should make efforts to obtain this, but approving as 1 is indeed sufficient at present.	yes
2017-04-20 23:12	jvalleroy	-	I have 1 signature by a DD, along with additional trust paths. Since I am applying for DM, this should be sufficient.	yes