• People
  • Site wizard
  • Wiki help
  • ascii
    DDPO Portfolio Contributor
  • Login
  1. Markus Schade
  2. Debian Maintainer
  3. 886: Key consistency checks

Key consistency checks

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

This process has been closed by noodles on 2021-03-24: no further modifications are possible.

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
  • 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 6694 5D2C 7458 AA54 4C7F F194 9FBB 5B02 7967 4636
Main key ok (last updated: 2025-05-02 02:51 UTC)
UID Markus Schade <marks, mschade.de> ok, 0 non-DD sigs, 0 DD sigs:
  • none
UID Markus Schade <marks, markusschade.com> ok, 0 non-DD sigs, 0 DD sigs:
  • none
UID Markus Schade <markus.schade, gmail.com> ok, 0 non-DD sigs, 0 DD sigs:
  • none

Active key endorsements

Endorsed by Date Statement Actions
ondrej 2021-02-28
(4 years, 2 months ago)
For nm.debian.org, at 2021-02-28:
For the past 7 years, I have worked with Markus Schade on yadifa and nsd.

For this past work, Markus Schade sent mails using the email address markus.schade@gmail.com
which is the one they're using on nm.debian.org, and they signed their work and
email using a GPG key with fingerprint 6694 5D2C 7458 AA54 4C7F  F194 9FBB 5B02 7967 4636.

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 Markus Schade as they
present themselves on nm.debian.org is the rightful owner of both email
markus.schade@gmail.com and GPG key 6694 5D2C 7458 AA54 4C7F  F194 9FBB 5B02 7967 4636.
Signed with key 30B9 33D8 0FCE 3D98 1A2D 38FB 0C99 B70E F4FC BB07
View raw

Log

Date Author Action Content Public
2021-03-02 06:17 santiago req_approve Requirement approved yes

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: , , , ,