Key consistency checks

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

This process has been closed by nm@debian.org on 2016-10-04: no further modifications are possible.

Potential problems

key has issues key_encryption_expires_soon key_size_3072

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	E966 46BE 08C0 AF0A A0F9 0788 A5FE EE3A C793 7444
Main key	key_encryption_expires_soon key_size_3072 (last updated: 2025-02-01 00:59 UTC)
UID Daniel Shahaf <d.s, daniel.shahaf.name>	ok, 0 non-DD sigs, 1 DD sigs: DFE691AE331BA3DB: James McCoy (Debian) <jamessan@debian.org>
UID Daniel Shahaf <danielsh, apache.org>	ok, 0 non-DD sigs, 1 DD sigs: DFE691AE331BA3DB: James McCoy (Debian) <jamessan@debian.org>

Active key endorsements

Endorsed by	Date	Statement	Actions

Log

Date	Author	Action	Content	Public
2016-09-25 18:12	noodles	req_approve	I think 3K is common enough that I doubt this is buying much (I've seen at least one person who did something similar, but had an entirely non-standard size), but as a key size it's fine for inclusion in the keyring.	yes
2016-09-25 17:21	jmw	-	Await input from keyring-maint	yes
2016-09-25 17:20	danielsh	-	When I created the key, I deliberately set its length to 3072R rather than 4096R to avoid cross-key attacks that only work when all attacked keys are about the same size. (For example, two RSA keys that share a prime are both trivially compromisable via gcd.)	yes