Key consistency checks

This requirement has been approved by Jonathan Wiltshire <jmw@debian.org> 3 months, 1 week ago.

This process has been closed by gwolf on 2025-04-26: 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	0B0B 6E49 4E9D 5EFB 3918 0D9A 2D19 2CA6 2477 0276
Main key	ok (last updated: 2025-05-30 02:54 UTC)
UID Mario Limonciello <superm1, gmail.com>	ok, 0 non-DD sigs, 2 DD sigs: 2CF0F17C43474B6F: Raúl Benencia <rul@kalgan.cc> 5ACE8D6E0C14A470: Luke Faraone <luke@faraone.cc>
UID Mario Limonciello <mario.limonciello, dell.com>	skip uid_revoked, 1 non-DD sigs, 2 DD sigs: C274DB64C2300F7B: Sjoerd Simons <sjoerd@luon.net> D14EF15DAFE11347: Martin Pitt <martin.pitt@ubuntu.com>
UID Mario Limonciello <superm1, kernel.org>	ok, 0 non-DD sigs, 0 DD sigs: none
UID Mario Limonciello <mario.limonciello, amd.com>	ok, 0 non-DD sigs, 0 DD sigs: none
UID Mario Limonciello <superm1, debian.org>	ok, 0 non-DD sigs, 0 DD sigs: none

Active key endorsements

Endorsed by

Date

Statement

Actions

93sam

2025-02-03
(4 months ago)

For nm.debian.org, at 2025-02-02:

For the past 10 years or so, I have worked with Mario Anthony
Limonciello in the debian-efi team on a variety of packages.

For recent past work, Mario Anthony Limonciello sent mails using the
email address superm1@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 0B0B 6E49 4E9D 5EFB 3918 0D9A 2D19 2CA6 2477 0276.

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 Mario
Anthony Limonciello as they present themselves on nm.debian.org is the
rightful owner of both email superm1@gmail.com and GPG key 0B0B 6E49
4E9D 5EFB 3918 0D9A 2D19 2CA6 2477 0276.

Signed with key CEBB 5230 1D61 7E91 0390 FE16 5879 7957 3442 684E

View raw

Log

Date	Author	Action	Content	Public
2025-02-28 20:10	jmw	req_approve	Requirement approved	yes