Key consistency checks
This
requirement has been approved by Santiago Ruano Rincón <santiagorr@riseup.net>
4 years, 10 months ago.
This
process has been closed by noodles on
2020-02-15: 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 |
1379 6755 BBC7 2BB8 ABE2 AEB5 FA9D EC5D E11C 63F1 |
Main key |
ok (last updated: 2024-12-20 07:33 UTC)
|
UID Emmanuel Arias <eamanu, riseup.net> |
ok, 0 non-DD sigs,
3 DD sigs:
- C0BA812C6C4DCB2E: Mathias Gibbens <mathias@calenhad.com>
- A3E3969F6DDEEC86: Andrey Rahmatullin <wrar@wrar.name>
- 2404C9546E145360: Gunnar Eyal Wolf Iszaevich <gwolf@iiec.unam.mx>
|
UID Emmanuel Arias (eamanu, eamanu.com) <emmanuelarias30, gmail.com> |
ok, 2 non-DD sigs,
3 DD sigs:
- AB645F406286A7D0: Lisandro Damián Nicanor Pérez Meyer <lisandro@debian.org>
- B490E3DF337F3213: Martin (Debian) <debacle@debian.org>
- C0BA812C6C4DCB2E: Mathias Gibbens <mathias@calenhad.com>
|
UID Emmanuel Arias (emmanuelarias30, gmail.com - eamanu, eamanu.com) <eamanu, yaerobi.com> |
ok, 2 non-DD sigs,
7 DD sigs:
- AB645F406286A7D0: Lisandro Damián Nicanor Pérez Meyer <lisandro@debian.org>
- 0B00FB6CEBE2D002: Ulises Vitulli <dererk@debian.org>
- B490E3DF337F3213: Martin (Debian) <debacle@debian.org>
- C0BA812C6C4DCB2E: Mathias Gibbens <mathias@calenhad.com>
- A3E3969F6DDEEC86: Andrey Rahmatullin <wrar@wrar.name>
- 2404C9546E145360: Gunnar Eyal Wolf Iszaevich <gwolf@iiec.unam.mx>
- AFCFEC8E669CE1C2: Graham Inggs <ginggs@riseup.net>
|
UID Emmanuel Arias <eamanu, debian.org> |
ok, 2 non-DD sigs,
5 DD sigs:
- B490E3DF337F3213: Martin (Debian) <debacle@debian.org>
- C0BA812C6C4DCB2E: Mathias Gibbens <mathias@calenhad.com>
- A3E3969F6DDEEC86: Andrey Rahmatullin <wrar@wrar.name>
- 2404C9546E145360: Gunnar Eyal Wolf Iszaevich <gwolf@iiec.unam.mx>
- AFCFEC8E669CE1C2: Graham Inggs <ginggs@riseup.net>
|
Active key endorsements
Endorsed by |
Date |
Statement |
Actions |
pollo |
2022-08-03 (2 years, 4 months ago) |
For nm.debian.org, at 2022-08-03:
For the past 18 months, I have worked with Emmanuel Arias on various packages in
the Python Team, mostly over IRC.
The first interaction over IRC I have had with Emmanuel Arias was on 2019-07-21
on the #debian-python channel. I've since then had frequent and regular
interactions with him in this channel. Although IRC messages are not signed by
an OpenPGP key, the nick Emmanuel Arias has been using (eamanu) is:
1. Registered on OFTC's NickServ
2. Consistent with his Salsa username (eamanu) and with his Debian username
(eamanu)
The first record of Emmanuel Arias signing an email with OpenPGP key "1379 6755
BBC7 2BB8 ABE2 AEB5 FA9D EC5D E11C 63F1" I have is on 2021-02-07. Since then,
he's written frequently on the debian-python mailing list using email address
<eamanu@yaerobi.com> and signs his mails most of the time.
Emmanuel Arias also signs his git commits. Although most of the mentorship I've
done for him has been answering questions on IRC, I have had the chance to work
closely with him on packages "poetry" and "poetry-core".
All the git commits made on these two packages by Emmanuel Arias were signed by
the OpenPGP key "1379 6755 BBC7 2BB8 ABE2 AEB5 FA9D EC5D E11C 63F1". The
oldest signed git commit Emmanuel Arias made on "poetry" was on 2020-03-31 and
the latest, on 2021-12-31. The oldest signed git commit he made on
"poetry-core" was on 2020-12-15 and the latest on 2022-08-01.
I've made sure that Emmanuel Arias is 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 Emmanuel Arias as
they present themselves on nm.debian.org is the rightful owner of both email
eamanu@yaerobi.com and GPG key 1379 6755 BBC7 2BB8 ABE2 AEB5 FA9D EC5D E11C
63F1.
Signed with key F64D 61D3 21F3 CB48 9156 753D E1E5 457C 8BAD 4113
|
View raw
|
Log
Date |
Author |
Action |
Content |
Public |
2020-02-05 15:18 |
santiago |
- |
Ah! Thanks for clarifying Mattia |
yes |
2020-02-05 13:40 |
mattia |
- |
The "no UID found that fully satisfies requirements" is just because there are no UIDs with 2 DD signatures, nothing more. Since this is a DM process, that's fine as it is, no need to change anything.
Also, this is GPG, once something is published it's not possible to take it back, so you can't possibly delete commens or UIDs at all (you can only revoke them). |
yes |
2020-02-05 13:25 |
santiago |
- |
I don't know it that would be even possible without deleting the uid. You could add an uid without comments, but of course you would need to ask to get it signed. |
yes |
2020-02-05 12:09 |
eamanu |
- |
I should remove the comments on the UIDs? |
yes |
2020-02-05 09:23 |
santiago |
- |
I've approved the key consistency, although nm.debian.org says "no UID found that fully satisfies requirements". If I'm not wrong, the comments in the UIDs that contain your email addresses are troublesome for the check. |
yes |
2020-02-05 07:58 |
santiago |
req_approve |
Requirement approved |
yes |
2020-02-05 03:45 |
eamanu |
- |
Hi,
I've just upload de signed key. |
yes |
2020-01-09 10:50 |
mattia |
- |
You'll need a DD signature on your key to proceed. |
yes |