Key consistency checks

This requirement looks ready for approval, but has not been approved yet.

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, or an Eliptic Curve based key
the key should have the sign, certify and encrypt capabilities (subkeys are encouraged)
for an RSA key, the primary cryptographic material should be at least 4096 bits
the UIDs used by an applicant to work in the project should be signed (certified) 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	3FA2 9177 F0E4 6DE9 134B 1418 04A0 DCF2 1891 3611
Main key	ok (last updated: 2026-10-27 00:24 UTC)
UID Michael Lloyd <michael, micl.dev>	ok, 1 non-DD sigs, 1 DD sigs: E86F1A6CF30FEA6D: Akash Santhosh <akash@debian.org>

Active key endorsements

Endorsed by	Date	Statement	Actions

Log

Date	Author	Action	Content	Public