Key consistency checks
This
requirement has been approved by Santiago Ruano Rincón <santiagorr@riseup.net>
1 year, 8 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 |
61C8 1DF2 2F4C 386D 0CCA BCA7 5291 703B FA09 034E |
| Main key |
ok (last updated: 2024-12-21 23:01 UTC)
|
| UID Carlos Henrique Lima Melara <charles, debian.org> |
ok, 0 non-DD sigs,
0 DD sigs:
|
| UID Carlos Henrique Lima Melara <charlesmelara, outlook.com> |
ok, 2 non-DD sigs,
4 DD sigs:
- FB0E132DDB0AA5B1: Daniel Lenharo de Souza <lenharo@debian.org>
- FC0DB1BBCD460BDE: Antonio Terceiro <asa@terceiro.xyz>
- 4B043FCDB9444540: Mattia Rizzolo <mattia@mapreri.org>
- B01D1A72AC8DC9A1: Jonathan Carter <jcc@debian.org>
|
| UID Carlos Henrique Lima Melara <charlesmelara, riseup.net> |
ok, 6 non-DD sigs,
first 10 of 15 DD sigs:
- F4E4ACDBB8D08BE0: Samuel Henrique <samueloph@debian.org>
- 84E624545A27D942: David da Silva Polverari <polverari@debian.org>
- 5A303591F8CDB08B: Thiago Andrade Marques (andrade) <andrade@debian.org>
- F823A2729883C97C: Lucas Kanashiro <kanashiro@debian.org>
- F4BAAA80DB28BA4C: Marcos Talau <talau@debian.org>
- D0EB762865FC5E36: Sergio Durigan Junior (Main UID) <sergiodj@sergiodj.net>
- 033C4CA276024834: Athos Ribeiro <athos.ribeiro@canonical.com>
- 9605A1098C63B92A: Edward Betts <edward@4angle.com>
- 57930DAB0B86B067: Joost E. van Baal (Nederland, 1970)
- EEED479E6CECF707: Ananthu C V <weepingclown@disroot.org>
|
Active key endorsements
| Endorsed by |
Date |
Statement |
Actions |
Log
| Date |
Author |
Action |
Content |
Public |
| 2023-04-21 12:08 |
santiago |
req_approve |
Requirement approved |
yes |
| 2023-04-12 20:48 |
charles |
- |
Hi, Pierre-Elliott. You are correct, I'm transitioning to charlesmelara@riseup.net as main uid. Now it should be ok, right? |
yes |
| 2023-04-12 11:38 |
peb |
- |
Hi,
Theoretically to approve your keychecks, you'd need at least one signature on the UID you intend to use for your Debian activities (charlesmelara@riseup.net). Yet, you have none on this one.
Do you intend to have a DD sig on this UID or an endorsement of your key? |
yes |