• People
  • Site wizard
  • Wiki help
  • gber
    DDPO Portfolio Contributor
  • Login
  1. Guido Berhörster
  2. Debian Maintainer
  3. 1442: Key consistency checks

Key consistency checks

This requirement looks incomplete.

Potential problems

  • 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, 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 8F33 352E B9A6 58B0 AA0D 9639 6BD6 02EF D4F9 F862
Main key ok (last updated: 2025-10-07 15:57 UTC)
UID Guido Berhoerster <guido, berhoerster.name> ok, 1 non-DD sigs, 0 DD sigs:
  • none
UID Guido Berhoerster <guido.berhoerster, gmx.net> ok, 1 non-DD sigs, 0 DD sigs:
  • none
UID Guido Berhoerster <guido.berhoerster, gmx.de> ok, 1 non-DD sigs, 0 DD sigs:
  • none
UID Guido Berhoerster <guido.berhoerster, arcor.de> ok, 1 non-DD sigs, 0 DD sigs:
  • none
UID Guido Berhoerster <ich, guido-berhoerster.org> ok, 1 non-DD sigs, 0 DD sigs:
  • none

Active key endorsements

Endorsed by Date Statement Actions
sunweaver 2025-10-10
(4 days, 16 hours ago)
For nm.debian.org, at 2025-10-10:
For the past 4 years, I have worked with Guido Berhörster on various OSS
projects in Debian and elsewhere. Esp. Guido has contributed
tremendously to the packaging of the Lomiri operatiring environment and
also to Lomiri upstream development.

For this past work, Guido Berhörster sent mails using the email address guido+debian@berhoerster.name
which is the one they're using on nm.debian.org, and they signed their work and
email using a GPG key with fingerprint 8F33 352E B9A6 58B0 AA0D  9639 6BD6 02EF D4F9 F862.

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 Guido Berhörster as they
present themselves on nm.debian.org is the rightful owner of both email
guido+debian@berhoerster.name and GPG key 8F33 352E B9A6 58B0 AA0D  9639 6BD6 02EF D4F9 F862.
Signed with key 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31
View raw

Log

Date Author Action Content Public

Copyright © 2012--2020 Debian Front Desk. Source code is available on Salsa. Report bugs on Salsa or the Debian BTS.

This page is also available in the following languages: , , , ,