Key consistency checks

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

This process has been closed by noodles on 2022-07-30: 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	DC07 18E3 22E2 C760 5EBD C831 4695 7EC0 8FD0 FE90
Main key	ok (last updated: 2024-10-04 03:45 UTC)
UID Robin Jarry <robin, jarry.cc>	ok, 0 non-DD sigs, 1 DD sigs: 061212944647A411: Pierre Gruet <pgt@debian.org>

Active key endorsements

Endorsed by

Date

Statement

Actions

nilesh

2022-07-18
(2 years, 3 months ago)

For nm.debian.org, at 2022-07-18:
For the past 8-9 months, since November last year, I have worked with Robin Jarry on buildbot and aerc.

For this past work, Robin Jarry sent mails using the email address robin@jarry.cc
which is the one they're using on nm.debian.org.

I have made the following checks for their keys:

1. Checked signs in atleast 5-6 emails (and commits) in past month

2. Checked their signed commits to the repositories. I checked several of his upstream project
   repositories releases like aerc, dlrepo, sysrepo-python etc. all of which are all signed with his gpg key.

3. Made sure that they are able to decrypt the messages sent to them with their GPG key

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 Robin Jarry as they
present themselves on nm.debian.org is the rightful owner of both email
robin@jarry.cc and GPG key DC07 18E3 22E2 C760 5EBD  C831 4695 7EC0 8FD0 FE90.

Signed with key 3E99 A526 F5DC C0CB BF1C EEA6 00BA E74B 3433 69F1

View raw

Log

Date	Author	Action	Content	Public
2022-07-25 16:04	santiago	req_approve	Requirement approved	yes