Key consistency checks
This
requirement has been approved by Mattia Rizzolo <mattia@debian.org>
3 years, 1 month ago.
This
process has been closed by gwolf on
2021-11-19: 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 |
4573 E9D2 AD27 DB89 6BBF 2F9E F15D CE53 1605 1F27 |
| Main key |
ok (last updated: 2024-12-18 19:40 UTC)
|
| UID Sergio de Almeida Cipriano Junior <sergiosacj, protonmail.com> |
ok, 3 non-DD sigs,
first 10 of 11 DD sigs:
- D0EB762865FC5E36: Sergio Durigan Junior (Main UID) <sergiodj@sergiodj.net>
- FB0E132DDB0AA5B1: Daniel Lenharo de Souza <lenharo@debian.org>
- 5291703BFA09034E: Carlos Henrique Lima Melara <charles@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>
- 348A778D6885EF8F: Jose M Calhariz (Técnico) <jose.calhariz@tecnico.ulisboa.pt>
- F4E4ACDBB8D08BE0: Samuel Henrique <samueloph@debian.org>
- EEED479E6CECF707: Ananthu C V <weepingclown@disroot.org>
|
| UID Sergio de Almeida Cipriano Junior <sergiosacj, riseup.net> |
ok, 3 non-DD sigs,
first 10 of 11 DD sigs:
- D0EB762865FC5E36: Sergio Durigan Junior (Main UID) <sergiodj@sergiodj.net>
- FB0E132DDB0AA5B1: Daniel Lenharo de Souza <lenharo@debian.org>
- 5291703BFA09034E: Carlos Henrique Lima Melara <charles@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>
- 348A778D6885EF8F: Jose M Calhariz (Técnico) <jose.calhariz@tecnico.ulisboa.pt>
- F4E4ACDBB8D08BE0: Samuel Henrique <samueloph@debian.org>
- EEED479E6CECF707: Ananthu C V <weepingclown@disroot.org>
|
Active key endorsements
| Endorsed by |
Date |
Statement |
Actions |
Log
| Date |
Author |
Action |
Content |
Public |
| 2021-11-04 22:23 |
mattia |
req_approve |
Requirement approved |
yes |
| 2021-11-04 22:01 |
sergiosacj |
- |
I edited the key but I didn't ask for a new signature, my fault, I updated the key with the signature. |
yes |
| 2021-11-04 10:17 |
mattia |
- |
I see that you are applying with an email that is different than the one with a single signature on. At the same time the same person who certified the key UID is advocating you using that other address. Did either of you forget to send a signature, or what? |
yes |