Key consistency checks

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

This process has been closed by noodles on 2023-01-24: no further modifications are possible.

Potential problems

no UID found that fully satisfies requirements

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	A34E 9DC3 AD34 D27F 17CF 36D2 3679 ECB8 7B7C EC0C
Main key	ok (last updated: 2024-12-14 22:44 UTC)
UID Israel Galadima <izzygaladima, gmail.com>	ok, 0 non-DD sigs, 0 DD sigs: none

Active key endorsements

Endorsed by

Date

Statement

Actions

praveen

2023-01-09
(1 year, 11 months ago)

For nm.debian.org, at 2023-01-09:
For the past 6+ months, I have worked with Israel Galadima on javascript team
maintained packages, especially a 3 month outreachy internship to create an apt
plugin for yarn package manager. He has continued contributions after the
outreachy period as well.

For this past work, Israel Galadima sent mails using the email address
izzygaladima@gmail.com which is the one they're using on nm.debian.org, and
they signed their work and email using a GPG key with fingerprint A34E 9DC3
AD34 D27F 17CF  36D2 3679 ECB8 7B7C EC0C.

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. Additionally
verified the email id with their matrix account by sending a secret code
encrypted to their email and verifying it on matrix.

Due to the long-term interactions we had, I'm convinced that Israel Galadima as
they present themselves on nm.debian.org is the rightful owner of both email
izzygaladima@gmail.com and GPG key A34E 9DC3 AD34 D27F 17CF  36D2 3679 ECB8
7B7C EC0C.

Signed with key D308 63E2 6020 E543 F471 9A83 8F53 E019 3B29 4B75

View raw

Log

Date	Author	Action	Content	Public
2023-01-16 09:22	santiago	req_approve	Requirement approved	yes