Key consistency checks

This requirement has been approved by Santiago Ruano Rincón <santiagorr@riseup.net> 5 years, 1 month ago.

This process has been closed by noodles on 2019-12-05: 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	D4EB 7D94 E78E 4EE8 ECE0 7F94 F879 6199 C045 86CE
Main key	ok (last updated: 2024-12-18 07:39 UTC)
UID Richard Laager <rlaager, debian.org>	ok, 0 non-DD sigs, 0 DD sigs: none
UID Richard Laager <rlaager, gmail.com>	ok, 0 non-DD sigs, 2 DD sigs: 11192892EFD75934: Kenneth J. Pronovici <pronovic@ieee.org> C9E55E2FADC8F4B9: Steve M. Robbins <steve@sumost.ca>
UID Richard Laager <rlaager, pidgin.im>	ok, 0 non-DD sigs, 2 DD sigs: 11192892EFD75934: Kenneth J. Pronovici <pronovic@ieee.org> C9E55E2FADC8F4B9: Steve M. Robbins <steve@sumost.ca>
UID Richard Laager <rlaager, wiktel.com>	ok, 0 non-DD sigs, 2 DD sigs: 11192892EFD75934: Kenneth J. Pronovici <pronovic@ieee.org> C9E55E2FADC8F4B9: Steve M. Robbins <steve@sumost.ca>
UID Richard Laager <rlaager, coderich.net>	ok, 0 non-DD sigs, 2 DD sigs: 11192892EFD75934: Kenneth J. Pronovici <pronovic@ieee.org> C9E55E2FADC8F4B9: Steve M. Robbins <steve@sumost.ca>

Active key endorsements

Endorsed by	Date	Statement	Actions

Log

Date	Author	Action	Content	Public
2019-11-19 11:11	mattia	-	considering that most keys don't have an expiry… :) (also I use a 10-years expiration myself for the master key)	yes
2019-11-18 22:35	santiago	-	I wonder if a ten-year key expiration date is really useful.	yes
2019-11-18 22:32	santiago	req_approve	Requirement approved	yes