Key consistency checks
This
requirement has been approved by Mattia Rizzolo <mattia@debian.org>
6 years, 3 months ago.
This
process has been closed by gwolf on
2019-05-09: 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 |
DF01 A922 9726 D0FA 42F7 5706 6DAC 3C44 8773 381A |
| Main key |
ok (last updated: 2025-05-10 04:28 UTC)
|
| UID Andy Li <andy, onthewings.net> |
ok, 1 non-DD sigs,
2 DD sigs:
- 036A9C25BF357DD4: Tianon Gravi <tianon@tianon.xyz>
- 2A40A2ECB8DAD8D5: gustavo panizzo <gfa@zumbi.com.ar>
|
| UID Andy Li <andyli, debian.org> |
ok, 0 non-DD sigs,
0 DD sigs:
|
Active key endorsements
| Endorsed by |
Date |
Statement |
Actions |
Log
| Date |
Author |
Action |
Content |
Public |
| 2019-01-11 16:55 |
mattia |
req_approve |
Requirement approved |
yes |
| 2019-01-11 16:18 |
andyli |
- |
hmm... I have just sent the key to keys.gnupg.net, pgp.mit.edu, and keyserver.ubuntu.com as well, clicked on the update button in https://nm.debian.org/process/573/keycheck, but the page still shows no new signature. |
yes |
| 2019-01-11 10:43 |
mattia |
- |
send it to the general keyserver network, as that's what is used to pull keys from for the purposes of this check :) |
yes |
| 2019-01-11 01:01 |
andyli |
- |
I've send my key with the 2nd DD signature to keyring.debian.org yesterday. I think it will take some time before it can be reflected in the nm interface. |
yes |
| 2019-01-05 04:40 |
andyli |
- |
Yes, I'm going to collect another DD signature next week. Thanks for the reminder :) |
yes |
| 2019-01-02 09:44 |
mattia |
- |
You'll need another DD signature to proceed. |
yes |