Key consistency checks

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

This process has been closed by noodles on 2023-02-03: 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	480C 30BE F106 8522 0CBF D5EE 8715 7C32 9108 F09E
Main key	ok (last updated: 2025-02-04 05:35 UTC)
UID Blake Lee <blake, volian.org>	ok, 0 non-DD sigs, 0 DD sigs: none

Active key endorsements

Endorsed by

Date

Statement

Actions

stephanlachnit

2023-01-28
(2 years ago)

For nm.debian.org, at 2023-01-28:
For the past 6 months, I have worked with Blake Lee on nala.

For this past work, Blake Lee sent mails using the email address blake@volian.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 480C 30BE F106 8522 0CBF  D5EE 8715 7C32 9108 F09E.

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 Blake Lee as they
present themselves on nm.debian.org is the rightful owner of both email
blake@volian.org and GPG key 480C 30BE F106 8522 0CBF  D5EE 8715 7C32 9108 F09E.

Signed with key BB45 B0B3 FF56 1BDB D45E E8A9 B35B 49EA 5D56 3EFE

View raw

Log

Date	Author	Action	Content	Public
2023-01-31 12:55	santiago	req_approve	Requirement approved	yes