Key consistency checks

This requirement has been approved by Pierre-Elliott Bécue <peb@debian.org> 4 years, 9 months ago.

This process has been closed by santiago on 2020-09-23: 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	76C2 82AB 9B59 447C 39B7 CEEA 0576 302F E189 D4D2
Main key	ok (last updated: 2025-02-01 16:09 UTC)
UID Andriy Grytsenko <andrej, rep.kiev.ua>	ok, 1 non-DD sigs, 5 DD sigs: D3E17383CFA7FF06: Anton Gladky <gladk@debian.org> EFDED44BCDFB68E9: Marcin Owsiany <marcin@owsiany.pl> DECF849AA6357FB7: Tobias Frost <tobi@coldtobi.de> 9605A1098C63B92A: Edward Betts <edward@4angle.com> 52E45D29AA34EFC5: Jonathan Bustillos <jathan@debian.org>

Active key endorsements

Endorsed by	Date	Statement	Actions

Log

Date	Author	Action	Content	Public
2020-04-29 10:28	peb	req_approve	Please consider adding an expiration date to both your main key and your encryption subkey as it's considered a good practice. And also consider creating a signing subkey. :) Anyway, your key meets the requirements!	yes