Key consistency checks
requirement has been approved by Santiago Ruano Rincón <email@example.com>
1 year, 1 month ago.
process has been closed by noodles on
2023-01-24: no further modifications are possible.
- no UID found that fully satisfies requirements
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
|2B4F 9EDC AE00 DEE4 D0D7 A6E5 8895 3E6F 011C DC96
ok (last updated: 2024-02-14 08:10 UTC)
|UID Douglas Kosovic (Debian) <doug, uq.edu.au>
ok, 0 non-DD sigs,
0 DD sigs:
Active key endorsements
(1 year, 1 month ago)
For nm.debian.org, at 2023-01-13:
For the past 5 years, I have worked with Douglas Kosovic on network-manager-l2tp.
For this past work, Douglas Kosovic sent mails using the email address firstname.lastname@example.org
which is the one he is using on nm.debian.org.
During that time, Douglas used a key with fingerprint
E48B D89A 1C51 BFA2 8413 D183 49A7 787E F8D3 C039.
His package uploads to mentors.d.o were signed with that key and
upstream releases were signed with this key as well, see e.g.
I encouraged him to apply for DM.
During that process, he created a new GPG key with stronger encryption and
fingerprint 2B4F 9EDC AE00 DEE4 D0D7 A6E5 8895 3E6F 011C DC96.
I've made sure that he is able to decrypt encrypted messages sent to this
new key and that he is able to sign messages with the same key.
Doug also sent a statement to me signed by his old key that he is now using the
new key including its fingerprint. So I'm confident that he controls both keys.
New releases of network-manager-l2tp also use his new key, see e.g.
Due to the long-term interactions we had, I'm convinced that Douglas Kosovic as he
presents himself on nm.debian.org is the rightful owner of both email
email@example.com and GPG key 2B4F 9EDC AE00 DEE4 D0D7 A6E5 8895 3E6F 011C DC96.
Signed with key 09B3 AC2E CB16 9C90 4345 CC54 6AE1 DF0D 608F 22DC
|Douglas, Michael mentions an old key in the statement he recently submitted. Do you still control that old key? If yes, would you mind cross-sign your two keys please?
|Thanks Douglas for contributing to the project and for applying to become DM. For your key, we require at least one signature or strong endorsement. Do you have any plans for that?