Key consistency checks
This
requirement has been approved by Jonathan McDowell <noodles@earth.li>
5 years, 8 months ago.
This
process has been closed by noodles on
2019-06-25: 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 |
2861 2573 17C7 AEE4 F880 497E C386 0AC5 9F57 4E3A |
| Main key |
ok (last updated: 2025-02-12 01:53 UTC)
|
| UID Bastian Germann |
ok, 0 non-DD sigs,
0 DD sigs:
|
| UID Bastian Germann <bage, linutronix.de> |
skip uid_revoked, 0 non-DD sigs,
2 DD sigs:
- 7B96E8162A8CF5D1: Sebastian Andrzej Siewior
- 0953ED7BAD69A1CB: Philipp Hug <debian@hug.cx>
|
| UID Bastian Germann <b.germann, linutronix.de> |
skip uid_revoked, 0 non-DD sigs,
2 DD sigs:
- 7B96E8162A8CF5D1: Sebastian Andrzej Siewior
- 0953ED7BAD69A1CB: Philipp Hug <debian@hug.cx>
|
| UID Bastian Germann <bastiangermann, fishpost.de> |
ok, 0 non-DD sigs,
1 DD sigs:
- 0953ED7BAD69A1CB: Philipp Hug <debian@hug.cx>
|
| UID Bastian Germann <bastian.germann, linutronix.de> |
skip uid_revoked, 0 non-DD sigs,
2 DD sigs:
- 7B96E8162A8CF5D1: Sebastian Andrzej Siewior
- 0953ED7BAD69A1CB: Philipp Hug <debian@hug.cx>
|
| UID bage, debian.org |
ok, 0 non-DD sigs,
0 DD sigs:
|
| UID Bastian Germann <bage, debian.org> |
ok, 0 non-DD sigs,
1 DD sigs:
- 4799A35146D12B35: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
|
Active key endorsements
| Endorsed by |
Date |
Statement |
Actions |
Log
| Date |
Author |
Action |
Content |
Public |
| 2019-06-04 19:46 |
noodles |
req_approve |
This is a manual check, with some automated guidance. The system likes at least 2 DD signatures - for a DM application this can be relaxed, but we still recommend you make an effort to gain additional signatures. Also your primary UID has no valid DD signatures. Again, not a show-stopper but something we recommend you fix in time. |
yes |
| 2019-06-04 19:41 |
bage |
- |
What is causing "no UID found that fully satisfies requirements"? The only thing that I can think of are the subkeys having only 3072 bits. But the primary key has 4096 bits and "hokey lint" does not complain. |
yes |