Key consistency checks

This requirement has been approved by Santiago Ruano Rincón <santiagorr@riseup.net> 1 year, 10 months ago.

This process has been closed by johns on 2023-04-24: 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	0CE0 6FE3 92AA 48F8 D22E 4471 F9EF 8EE0 C021 630F
Main key	ok (last updated: 2024-12-30 14:31 UTC)
UID Cordell Bloor <cgmb, slerp.xyz>	ok, 0 non-DD sigs, 2 DD sigs: E76004C5CEF0C94C: Christian Kastner <ckk@kvr.at> 62645EB35F686A8A: Zhou Mo (Passport) <cdluminate@gmail.com>
UID Cordell Bloor <cgbloor, ucalgary.ca>	ok, 0 non-DD sigs, 0 DD sigs: none

Active key endorsements

Endorsed by

Date

Statement

Actions

ckk

2023-03-25
(1 year, 9 months ago)

For nm.debian.org, at 2023-03-24:
For the past 8 months, I have worked with Cordell Bloor on various components
of the ROCM ecosystem.

For this past work, Cordell Bloor sent mails using the email address
cgmb@slerp.xyz which is the one he is using on nm.debian.org and mentors.d.n,
and he signed his work and email using a GPG key with fingerprint
0CE0 6FE3 92AA 48F8 D22E  4471 F9EF 8EE0 C021 630F. Cordell Bloor also pointed
me to his GitHub page, where he has been signing tags with this key for many
years.

I've made sure that he is able to decrypt encrypted messages sent to this key
and that his is able to sign messages with the same key.

Due to the long-term interactions we had, I'm convinced that Cordell Bloor as he
presents himself on nm.debian.org is the rightful owner of both email
cgmb@slerp.xyz and GPG key 0CE0 6FE3 92AA 48F8 D22E  4471 F9EF 8EE0 C021 630F.

Signed with key 08F0 84DA 146C 873C 361A AFA8 E760 04C5 CEF0 C94C

View raw

emollier

2023-02-12
(1 year, 10 months ago)

For nm.debian.org, at 2023-02-12:
For the past year, I have worked with Cordell Bloor on packaging
ROCm components.

For this past work, Cordell Bloor sent mails using the email
address cgmb@slerp.xyz which is the one he is using on
nm.debian.org, and he signed his work uploaded to mentors.d.n
and a few emails using a GPG key with fingerprint
0CE0 6FE3 92AA 48F8 D22E  4471 F9EF 8EE0 C021 630F.

I've made sure that he is able to decrypt encrypted messages
sent to this key and that he is able to sign messages with the
same key.

Due to the long-term interactions we had, I'm convinced that
Cordell Bloor as he presents himself on nm.debian.org is the
rightful owner of both email cgmb@slerp.xyz and GPG key
0CE0 6FE3 92AA 48F8 D22E  4471 F9EF 8EE0 C021 630F.

Signed with key 8F91 B227 C7D6 F2B1 948C 8236 793C F67E 8F0D 11DA

View raw

Log

Date	Author	Action	Content	Public
2023-02-16 09:25	santiago	req_approve	Requirement approved	yes