Key consistency checks

This requirement has been approved by Pierre-Elliott Bécue <peb@debian.org> 1 year, 6 months ago.

This process has been closed by johns on 2024-05-03: 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, or an Eliptic Curve based key
the key should have the sign, certify and encrypt capabilities (subkeys are encouraged)
for an RSA key, the primary cryptographic material should be at least 4096 bits
the UIDs used by an applicant to work in the project should be signed (certified) 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	3B57 CBBD D2B7 9ED8 50E4 9CB8 6FA8 7A15 232F A178
Main key	ok (last updated: 2025-11-04 11:29 UTC)
UID Bernhard Miklautz <bernhard.miklautz, shacknet.at>	ok, 1 non-DD sigs, 3 DD sigs: DEE8043EE17EBB30: Rhonda 357312559D1E064B: Ondřej Nový <novy@ondrej.org> 9AF46B3025771B31: Mike Gabriel <mike.gabriel@das-netzwerkteam.de>
UID Bernhard Miklautz <bernhard.miklautz, thincast.com>	ok, 1 non-DD sigs, 3 DD sigs: DEE8043EE17EBB30: Rhonda 357312559D1E064B: Ondřej Nový <novy@ondrej.org> 9AF46B3025771B31: Mike Gabriel <mike.gabriel@das-netzwerkteam.de>

Active key endorsements

Endorsed by

Date

Statement

Actions

zeha

2024-04-17
(1 year, 6 months ago)

For nm.debian.org, at 2024-04-17:
For the past ten years, I have worked with Bernhard Miklautz on Debian, FreeRDP
and other professional work.

For this past work, Bernhard Miklautz sent mails using the email address
bernhard.miklautz@shacknet.at which is the one they're using on nm.debian.org,
and they signed their work and email using a GPG key with fingerprint
3B57 CBBD D2B7 9ED8 50E4  9CB8 6FA8 7A15 232F A178.

I've made sure that they are able to decrypt encrypted messages sent to this
key and that they're able to sign messages with the same key.

Due to the long-term interactions we had, I'm convinced that Bernhard Miklautz
as they present themselves on nm.debian.org is the rightful owner of both email
bernhard.miklautz@shacknet.at and GPG key 3B57 CBBD D2B7 9ED8 50E4  9CB8 6FA8 7A15 232F A178.

Signed with key 7D1A CFFA D9E0 806C 9C4C D392 5C13 D6DB 9305 2E03

View raw

Log

Date	Author	Action	Content	Public
2024-05-03 09:53	peb	req_approve	Requirement approved	yes