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	95FF E836 21AD DF94 0F73 00FC AA1F 6DCF 461A 82FD
Main key	ok (last updated: 2026-05-23 01:11 UTC)
UID Brian Cosgrove <cosgroveb, gmail.com>	ok, 0 non-DD sigs, 1 DD sigs: 7541CFAAFC35EACF: Stephen Gelman <ssgelm@gmail.com>

Active key endorsements

Endorsed by

Date

Statement

Actions

ssgelm

2026-05-23
(5 hours, 4 minutes ago)

For nm.debian.org, at 2026-05-23:
For the past few months, I have worked with Brian Cosgrove on packaging clnkr.

For this past work, Brian Cosgrove sent mails using the email address cosgroveb@gmail.com
which is the one they're using on nm.debian.org, and they signed their work and
email using a GPG key with fingerprint 95FF E836 21AD DF94 0F73  00FC AA1F 6DCF 461A 82FD.
An example of a contribution signed with that key can be found at:
https://github.com/clnkr-ai/clnkr/commit/ebfc845f9803ae57a4605c4cf941d1405f104e8f

I've made sure that they are able to decrypt encrypted messages sent to this key
and that they're able to sign messages with the same key.

Due to the long-term interactions we had, I'm convinced that Brian Cosgrove as they
present themselves on nm.debian.org is the rightful owner of both email
cosgroveb@gmail.com and GPG key 95FF E836 21AD DF94 0F73  00FC AA1F 6DCF 461A 82FD.

Signed with key 0BBE EEF0 64E9 4ABE 8432 58B4 7541 CFAA FC35 EACF

View raw

Log

Date	Author	Action	Content	Public