Key consistency checks
This
requirement has been approved by Mattia Rizzolo <mattia@debian.org>
5 years, 5 months ago.
This
process has been closed by noodles on
2019-12-19: 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 |
522D 7163 831C 73A6 35D1 2FE5 EC37 1482 9567 81AF |
Main key |
ok (last updated: 2025-01-22 13:06 UTC)
|
UID Sven Eckelmann <sven, narfation.org> |
ok, 0 non-DD sigs,
2 DD sigs:
- A73E0055558FB8DD: Jan Dittberner <jan@dittberner.info>
- A459EC6715B0705F: Thorsten Alteholz <debian@alteholz.de>
|
UID Sven Eckelmann <lazhur, gmx.de> |
skip uid_revoked, 0 non-DD sigs,
0 DD sigs:
|
UID Sven Eckelmann <sven.eckelmann, gmx.de> |
skip uid_revoked, 0 non-DD sigs,
0 DD sigs:
|
UID Sven Eckelmann <ecsv, hrz.tu-chemnitz.de> |
skip uid_revoked, 0 non-DD sigs,
0 DD sigs:
|
UID Sven Eckelmann <ecsv, informatik.tu-chemnitz.de> |
skip uid_revoked, 0 non-DD sigs,
0 DD sigs:
|
UID Sven Eckelmann <sven.eckelmann, s2004.tu-chemnitz.de> |
skip uid_revoked, 0 non-DD sigs,
0 DD sigs:
|
UID Sven Eckelmann <sven.eckelmann, informatik.tu-chemnitz.de> |
skip uid_revoked, 0 non-DD sigs,
0 DD sigs:
|
UID Sven Eckelmann <sven.eckelmann, sinformatik.tu-chemnitz.de> |
skip uid_revoked, 0 non-DD sigs,
0 DD sigs:
|
UID Sven Eckelmann <sven, open-mesh.com> |
ok, 0 non-DD sigs,
1 DD sigs:
- A459EC6715B0705F: Thorsten Alteholz <debian@alteholz.de>
|
UID Sven Eckelmann <sven.eckelmann, open-mesh.com> |
ok, 0 non-DD sigs,
1 DD sigs:
- A459EC6715B0705F: Thorsten Alteholz <debian@alteholz.de>
|
UID Sven Eckelmann <sven.eckelmann, openmesh.com> |
ok, 0 non-DD sigs,
1 DD sigs:
- A459EC6715B0705F: Thorsten Alteholz <debian@alteholz.de>
|
UID Sven Eckelmann <seckelmann, datto.com> |
ok, 0 non-DD sigs,
1 DD sigs:
- A459EC6715B0705F: Thorsten Alteholz <debian@alteholz.de>
|
UID Sven Eckelmann <se, simonwunderlich.de> |
ok, 0 non-DD sigs,
1 DD sigs:
- A459EC6715B0705F: Thorsten Alteholz <debian@alteholz.de>
|
Active key endorsements
Endorsed by |
Date |
Statement |
Actions |
Log
Date |
Author |
Action |
Content |
Public |
2019-08-19 09:08 |
mattia |
req_approve |
Requirement approved |
yes |
2019-07-28 13:52 |
ecsv |
- |
I've changed my key in 2011-05-08 (rt.debian.org #3108) with two DD signatures
> Debian developer Jan Dittberner (jandd) with fingerprint
> B2FF 1D95 CE8F 7A22 DF4C F09B A73E 0055 558F B8DD
> and Luca Capello (gismo) with fingerprint
> C331 BA3F 75FB 723B 5873 785B 06EA A066 E397 832F
> signed the key.
Looks like Luca Capello (gismo) has now the status DD emeritus (since 2019-04-12) and thus isn't counted by this automatic system. |
yes |