Key consistency checks
This
requirement has been approved by Santiago Ruano Rincón <santiagorr@riseup.net>
9 months ago.
This
process has been closed by johns on
2024-03-20: 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 |
6B2C EE37 C82C F91E 42A3 F84D 0B8D 1771 55F6 646E |
Main key |
ok (last updated: 2024-11-21 03:41 UTC)
|
UID Jean Charles Delépine <jean.charles, delepine.info> |
ok, 0 non-DD sigs,
1 DD sigs:
- 648047B2D723891C: Jean-Philippe MENGUAL (Debian) <jpmengual@debian.org>
|
UID Jean Charles Delépine <jean.charles.delepine, u-picardie.fr> (At work, officielle) |
ok, 0 non-DD sigs,
1 DD sigs:
- 648047B2D723891C: Jean-Philippe MENGUAL (Debian) <jpmengual@debian.org>
|
UID Jean Charles Delépine <delepine, nnx.com> (Historique) |
ok, 0 non-DD sigs,
1 DD sigs:
- 648047B2D723891C: Jean-Philippe MENGUAL (Debian) <jpmengual@debian.org>
|
UID Jean Charles Delépine <delepine, u-picardie.fr> (At work) |
ok, 0 non-DD sigs,
1 DD sigs:
- 648047B2D723891C: Jean-Philippe MENGUAL (Debian) <jpmengual@debian.org>
|
Active key endorsements
Endorsed by |
Date |
Statement |
Actions |
georgesk |
2024-02-09 (9 months, 4 weeks ago) |
For nm.debian.org, at 2024-02-08:
For the past two months, I have received a valuable help from Jean Charles Delépine on package wims, which I did not update for two years.
He tackled out some tough issues, and the package is in synchronization with upstream again.
For this past work, Jean Charles Delépine sent mails using the email address jean.charles@delepine.info
which is the one he is using on nm.debian.org, and he signed his work and
email using a GPG key with fingerprint 6B2C EE37 C82C F91E 42A3 F84D 0B8D 1771 55F6 646E.
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 Jean Charles Delépine as he
presents himself on nm.debian.org is the rightful owner of both email
jean.charles@delepine.info and GPG key 6B2C EE37 C82C F91E 42A3 F84D 0B8D 1771 55F6 646E.
Signed with key 3340 B364 FF67 153F B7CC AE85 1C28 1690 7136 AE39
|
View raw
|
Log
Date |
Author |
Action |
Content |
Public |
2024-03-02 11:15 |
santiago |
req_approve |
Requirement approved |
yes |