• People
  • Site wizard
  • Wiki help
  • plenae
    DDPO Portfolio Contributor
  • Login
  1. Pieter Lenaerts
  2. Debian Maintainer
  3. 1529: Key consistency checks

Key consistency checks

This requirement has been approved by Mattia Rizzolo <mattia@debian.org> 1 week, 3 days ago.

This process has been approved by mattia on 2026-04-16: 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 2B2E 0E3F B52F 5A53 164C ABCA 05B8 F2B0 72A0 E0EB
Main key ok (last updated: 2026-04-04 21:06 UTC)
UID Pieter Lenaerts <plenae, disroot.org> ok, 0 non-DD sigs, 2 DD sigs:
  • 31F3144544A1741A: Alexandre Detiste <alexandre.detiste@gmail.com>
  • E7BFC8EC95861109: Ben Hutchings <bwh@kernel.org>

Active key endorsements

Endorsed by Date Statement Actions
eamanu 2026-04-07
(2 weeks, 5 days ago)
For nm.debian.org, at 2026-04-06:
For the past 7 months, I have worked with Pieter Lenaerts on python-ldap and beets packages

Pieter demonstrated solid knowledge of the packages that Piter maintains.

For this past work, Pieter Lenaerts sent mails using the email address plenae@disroot.org
which is the one they're using on nm.debian.org, and they signed their work and
email using a GPG key with fingerprint 2B2E 0E3F B52F 5A53 164C  ABCA 05B8 F2B0 72A0 E0EB.

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 Pieter Lenaerts as they
present themselves on nm.debian.org is the rightful owner of both email
plenae@disroot.org and GPG key 2B2E 0E3F B52F 5A53 164C  ABCA 05B8 F2B0 72A0 E0EB.
Signed with key 1379 6755 BBC7 2BB8 ABE2 AEB5 FA9D EC5D E11C 63F1
View raw

Log

Date Author Action Content Public
2026-04-16 11:51 mattia 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: , , , ,