• People
  • Site wizard
  • Wiki help
  • mzf
    DDPO Portfolio Contributor
  • Login
  1. François Mazen
  2. Debian Maintainer
  3. 785: Key consistency checks

Key consistency checks

This requirement has been approved by Pierre-Elliott Bécue <peb@debian.org> 4 years, 9 months ago.

This process has been closed by noodles on 2020-08-11: 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 86A5 ABD6 FFDB 0A0C 7F50 57D3 4797 FA72 1C35 1C9E
Main key ok (last updated: 2025-05-05 09:17 UTC)
UID Francois Mazen <mzf, debian.org> ok, 0 non-DD sigs, 0 DD sigs:
  • none
UID Francois Mazen <francois, mzf.fr> ok, 2 non-DD sigs, 7 DD sigs:
  • 6B7498FCB9B358AC: Frédéric Bonnard <frediz@debian.org>
  • DECF849AA6357FB7: Tobias Frost <tobi@coldtobi.de>
  • B35B49EA5D563EFE: Stephan Lachnit <stephanlachnit@debian.org>
  • 793CF67E8F0D11DA: Étienne Mollier <emollier@emlwks999.eu>
  • B82A217AFDFE09F2: David Prévot <david@tilapin.org>
  • CC8C6BDD1403F4CA: Timo Röhling <timo@gaussglocke.de>
  • 9C5C99EB05BD750A: Paul Gevers <elbrus@debian.org>

Active key endorsements

Endorsed by Date Statement Actions

Log

Date Author Action Content Public
2020-07-29 10:18 peb req_approve Requirement approved yes
2020-07-28 20:49 mzf - Sending the key to keyserver.ubuntu.com has worked, thanks for the help santiago. yes
2020-07-28 20:06 mzf - The key has been signed by a Debian developer, but nm.debian.org website does not found it: http://keys.gnupg.net/pks/lookup?op=vindex&fingerprint=on&search=0x4797FA721C351C9E I've tried to push it directly on Debian Public Key Server: gpg --keyserver keyring.debian.org --send-keys 0x4797fa721c351c9e but still not found by the nm.debian.org website. Did I miss something? Thanks, François yes
2020-07-28 11:46 santiago - Thanks for contributing to Debian. Applying for Debian Maintainer requires at least one signature from an existing member. Do you have any plans to fulfill this requirement? 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: , , , ,