Key consistency checks

This requirement has been approved by Santiago Ruano Rincón <santiagorr@riseup.net> 4 years, 9 months ago.

This process has been closed by noodles on 2020-04-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	3CB7 C302 AFB5 7E61 A8C6 17DD 634E A55D 902B 9836
Main key	ok (last updated: 2025-01-27 07:51 UTC)
UID Dennis Braun <snd, debian.org>	ok, 0 non-DD sigs, 0 DD sigs: none
UID Dennis Braun <d_braun, kabelmail.de>	ok, 0 non-DD sigs, 5 DD sigs: D0AAB32A23B5397C: Henning Glawe <glawe@web.de> DECF849AA6357FB7: Tobias Frost <tobi@coldtobi.de> D04BA3A00125D5C0: Philip Hands <phil@hands.com> 4C5A6BAB12D2A7AE: Christoph Berg <cb@df7cb.de> B82A217AFDFE09F2: David Prévot <david@tilapin.org>
UID DNS (Debian) <debian, 88it.de>	skip uid_revoked, 0 non-DD sigs, 0 DD sigs: none
UID Dennis Braun <snd, y0o.de>	ok, 0 non-DD sigs, 4 DD sigs: D04BA3A00125D5C0: Philip Hands <phil@hands.com> 4C5A6BAB12D2A7AE: Christoph Berg <cb@df7cb.de> DECF849AA6357FB7: Tobias Frost <tobi@coldtobi.de> B82A217AFDFE09F2: David Prévot <david@tilapin.org>

Active key endorsements

Endorsed by

Date

Statement

Actions

sramacher

2021-08-10
(3 years, 5 months ago)

For nm.debian.org, at 2021-08-10:
For the past 20 months or so, I have worked with Dennis Braun on plenty of packages
maintained by the multimedia team.

For this past work, Dennis Braun sent mails using the email address d_braun@kabelmail.de
which is the one they're using on nm.debian.org, and they signed their work and
email using a GPG key with fingerprint 3CB7 C302 AFB5 7E61 A8C6  17DD 634E A55D 902B 9836.

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 Dennis Braun as they
present themselves on nm.debian.org is the rightful owner of both email
d_braun@kabelmail.de and GPG key 3CB7 C302 AFB5 7E61 A8C6  17DD 634E A55D 902B 9836.

Signed with key F78C BA07 817B B149 A11D 3390 69F2 FC51 6EA7 1993

View raw

Log

Date	Author	Action	Content	Public
2020-04-20 18:50	santiago	req_approve	Requirement approved	yes