Key consistency checks
This
requirement has been approved by Jonathan McDowell <noodles@earth.li>
8 years, 7 months ago.
This
process has been closed by jmw on
2017-09-13: no further modifications are possible.
Potential problems
- key has issues 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 |
6A3C 67D7 F011 900C C539 248B DFF3 AB37 4F16 F73A |
| Main key |
key_size_3072 (last updated: 2025-05-11 17:47 UTC)
|
| UID Anders Kaseorg <andersk, mit.edu> |
ok, 0 non-DD sigs,
3 DD sigs:
- 64959FE9838DF19C: Anne Christine Spang <christine@spang.cc>
- 283681BA6FE7F41D: Sam Hartman <hartmans@debian.org>
- BBC756DDBE595F6B: Alexander Chernyakhovsky <achernya@mit.edu>
|
| UID Anders Kaseorg <anders, kaseorg.com> |
ok, 0 non-DD sigs,
4 DD sigs:
- 64959FE9838DF19C: Anne Christine Spang <christine@spang.cc>
- 283681BA6FE7F41D: Sam Hartman <hartmans@debian.org>
- BBC756DDBE595F6B: Alexander Chernyakhovsky <achernya@mit.edu>
- BBC756DDBE595F6B: Alexander Chernyakhovsky <achernya@mit.edu>
|
Active key endorsements
| Endorsed by |
Date |
Statement |
Actions |
Log
| Date |
Author |
Action |
Content |
Public |
| 2016-10-06 19:37 |
noodles |
req_approve |
Key is sufficiently strong and already part of the DM keyring. |
yes |
| 2016-10-04 06:37 |
andersk |
- |
My current key is actually RSA 3072, despite the key_size_2048 claimed by this interface. I created it before Debian published the RSA 4096 recommendation, on the grounds that RSA 3072 is believed roughly comparable in strength to AES 128. I will create a new key if requested (though I may not be able to collect as many DD signatures as I have now), but if not, I’d prefer to wait for Ed25519. |
yes |