Key consistency checks

This requirement looks ready for approval, but has not been approved yet.

This process has been closed by nm@debian.org on 2022-07-22: 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	E252 1CB8 1757 36A9 7052 B2F8 954E 6A70 1005 98A2
Main key	ok (last updated: 2025-05-05 07:26 UTC)
UID Bo YU <tsu.yubo, gmail.com>	ok, 2 non-DD sigs, first 10 of 17 DD sigs: 664F1238AA8F138A: Daniel Lange <DLange@debian.org> 00186602339240CB: xiao sheng wen(肖盛文) (DD email) <atzlinux@debian.org> 68C078BE88F80CDA: Noèl Köthe <noel@debian.org> 27DE3D45104886EF: Santiago Ruano Rincón <santiagorr@riseup.net> 196418AAEB74C8A1: Jonathan Wiltshire <jmw@debian.org> 2A27904BD7243EDA: Nilesh Patra <nilesh@fsfe.org> 223AE055BD94E154: Milan Kupcevic <milan@debian.org> 44173FA13D058888: Ying-Chun Liu (PaulLiu) <paulliu@debian.org> 14135D277B88D7E5: YunQiang Su <wzssyqa@gmail.com> C0BA812C6C4DCB2E: Mathias Gibbens <mathias@calenhad.com>

Active key endorsements

Endorsed by

Date

Statement

Actions

byang

2023-08-30
(1 year, 8 months ago)

For nm.debian.org, at 2023-08-30:
For the past year, I have worked with Bo YU on some python packages
as well as collaboration in debian-riscv mailing list.

For this past work, Bo YU sent mails using the email address tsu.yubo@gmail.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 E252 1CB8 1757 36A9 7052  B2F8 954E 6A70 1005 98A2.

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 Bo YU as they
present themselves on nm.debian.org is the rightful owner of both email
tsu.yubo@gmail.com and GPG key E252 1CB8 1757 36A9 7052  B2F8 954E 6A70 1005 98A2.

Signed with key 7E77 2947 6D87 D6F1 1D91 ACCB C293 E7B4 6182 5ACE

View raw

Log

Date	Author	Action	Content	Public