Key consistency checks

This requirement has been approved by Santiago Ruano Rincón <santiagorr@riseup.net> 3 days, 20 hours ago.

This process has been approved by santiago on 2026-10-02: 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	633E 7738 5959 18C4 270E 473B ECFF 3EB4 030E 6E7E
Main key	ok (last updated: 2026-09-21 15:32 UTC)
UID Michele Cane <michele.cane, proton.me>	ok, 0 non-DD sigs, 1 DD sigs: D929F2992BEF0A33: Didier Raboud <didier@raboud.com>

Active key endorsements

Endorsed by

Date

Statement

Actions

jcfp

2026-09-19
(2 weeks, 3 days ago)

For nm.debian.org, at 2026-09-19:
For the past 3 months, I have worked with Michele Cane on multiple packages in the Python team.

For this past work, Michele Cane sent mails using the email address michele.cane@proton.me and he
signed his work using GPG key with fingerprint 633E 7738 5959 18C4 270E  473B ECFF 3EB4 030E 6E7E.

Public examples of signed mails and git commits are visible here:
https://salsa.debian.org/python-team/packages/python-asyncudp/-/commits/debian/master
https://salsa.debian.org/python-team/packages/python-raygeo/-/commits/debian/master
https://lists.debian.org/debian-python/2026/05/msg00029.html
https://lists.debian.org/debian-python/2026/07/msg00021.html
https://lists.debian.org/debian-python/2026/08/msg00102.html

I've made sure that he is able to decrypt encrypted messages sent to this key and that he's able
to sign messages with the same key. Due to the long-term interactions we had, I'm convinced that
Michele Cane as he presents himself on nm.debian.org is the rightful owner of both email address
michele.cane@proton.me and GPG key 633E 7738 5959 18C4 270E  473B ECFF 3EB4 030E 6E7E.

Signed with key D3F0 E02E C45A 938E 1D67 229E C434 9665 5925 B604

View raw

Log

Date	Author	Action	Content	Public
2026-10-02 14:07	santiago	req_approve	Requirement approved	yes