Key consistency checks

This requirement has been approved by Jonathan Wiltshire <jmw@debian.org> 3 months, 3 weeks ago.

This process has been closed by johns on 2025-02-18: 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	4A5F D1CD 1150 87CC 03DC 35C1 D597 8972 06C5 F07F
Main key	ok (last updated: 2025-05-09 02:37 UTC)
UID Maytham Alsudany <maytham, debian.org>	ok, 0 non-DD sigs, 0 DD sigs: none
UID Maytham Alsudany <maytha8thedev, gmail.com>	ok, 0 non-DD sigs, 0 DD sigs: none

Active key endorsements

Endorsed by

Date

Statement

Actions

tar

2024-04-15
(1 year ago)

For nm.debian.org, at 2024-04-15:
For the past ~9 months, I have worked with Maytham Alsudany on go packages.

For this past work, Maytham Alsudany sent mails using the email address maytha8thedev@gmail.com
which is the one they're using on nm.debian.org.

I have made the following checks for their keys:

1. All their mails both private and on mailing list are signed with their GPG key.

2. Checked their signed commits to the repositories they committed recently to.

3. Made sure that they are able to decrypt the messages sent to them with their GPG key.

Due to the long-term interactions we had, I'm convinced that Maytham Alsudany as they
present themselves on nm.debian.org is the rightful owner of both email
maytha8thedev@gmail.com and GPG key 4A5F D1CD 1150 87CC 03DC  35C1 D597 8972 06C5 F07F.

Signed with key B60A 1BF3 63DC 1319 FF0A 8E89 1168 52BC DF75 15C0

View raw

nilesh

2024-04-08
(1 year, 1 month ago)

For nm.debian.org, at 2024-04-08:
For the past 6-7 months, I have worked with Maytham Alsudany on Kitty and other go packages.

For this past work, Maytham Alsudany sent mails using the email address maytha8thedev@gmail.com
which is the one they're using on nm.debian.org.

I have made the following checks for their keys:

1. All their mails both private and on mailing list are signed with their GPG key.

2. Checked their signed commits to the repositories they committed recently to.

3. Made sure that they are able to decrypt the messages sent to them with their GPG key.

Due to the long-term interactions we had, I'm convinced that Maytham Alsudany as they
present themselves on nm.debian.org is the rightful owner of both email
maytha8thedev@gmail.com and GPG key 4A5F D1CD 1150 87CC 03DC  35C1 D597 8972 06C5 F07F.

Signed with key A095 B66E E090 24BE E6A2 F072 2A27 904B D724 3EDA

View raw

Log

Date	Author	Action	Content	Public
2025-01-15 14:32	jmw	req_approve	Requirement approved	yes