Key consistency checks

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

This process has been closed by peb on 2024-01-18: no further modifications are possible.

Potential problems

no UID found that fully satisfies requirements

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	8ED5 FF85 EB6D 58F5 0164 0246 CE7C 4AAD EA63 7685
Main key	ok (last updated: 2024-11-21 16:44 UTC)
UID Dato Simó <dato, net.com.org.es>	ok, 8 non-DD sigs, 0 DD sigs: none
UID Dato Simó <dato, debian.org>	ok, 8 non-DD sigs, 0 DD sigs: none

Active key endorsements

Endorsed by	Date	Statement	Actions

Log

Date	Author	Action	Content	Public
2022-06-18 11:36	mattia	-	Also as it stays in the log: we did check with keyring-maint before the approval, and Noodles agreed on IRC this is fine.	yes
2022-06-04 13:11	dato	-	Copy-pasting what I mentioned via e-mail, so that it’s registered in NM’s history: “Note that (in case it helps) this 4096-bit key is signed with my old 1024-bit key 0xDA6AE621, and it made it into the official DD keyring before I became emeritus; so it was accepted properly by keyring-maint as a substitute back then.”	yes
2022-06-03 10:22	santiago	req_approve	Requirement approved	yes
2022-06-02 12:41	santiago	-	It is great your coming back, dato! Regarding your key, it doesn't have signatures from keys found in the current DD keyring. If I am not wrong, at least two active DDs have previously signed your key, with their old keys. Could you please ask them if they are happy to sign your key again (with their new key)? Thank you, -- Santiago	yes