Key consistency checks

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

This process has been closed by noodles on 2022-05-23: 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	4A31 DB5A 1EE4 096C 8739 9880 9036 4929 4C33 F9B7
Main key	ok (last updated: 2024-10-03 20:41 UTC)
UID Lance Lin <lqi254, protonmail.com>	ok, 0 non-DD sigs, 0 DD sigs: none
UID Lance Lin <lq27267, gmail.com>	ok, 0 non-DD sigs, 0 DD sigs: none

Active key endorsements

Endorsed by

Date

Statement

Actions

bage

2022-11-18
(1 year, 11 months ago)

For nm.debian.org, at 2022-11-18:
For the past 2 months, I have worked with Lance Lin on anacron, usbredir, and workflow.

For this past work, Lance Lin sent mails using the email address LQi254@protonmail.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 4A31 DB5A 1EE4 096C 8739  9880 9036 4929 4C33 F9B7.

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 (more than two months but previous to that with
another key), I'm convinced that Lance Lin as they present themselves on nm.debian.org is
the rightful owner of both email LQi254@protonmail.com and GPG key
4A31 DB5A 1EE4 096C 8739  9880 9036 4929 4C33 F9B7.

Signed with key 2861 2573 17C7 AEE4 F880 497E C386 0AC5 9F57 4E3A

View raw

Log

Date	Author	Action	Content	Public
2022-05-23 09:37	santiago	req_approve	Requirement approved	yes
2022-05-16 14:31	santiago	-	Thanks for your Debian work and for applying to become DM. However, your gpg key doesn't have any signature or endorsement from DDs. Do you have a plan to solve that?	yes