Key consistency checks

This requirement looks incomplete.

This process has been closed by jmw on 2019-02-03: no further modifications are possible.

Potential problems

no UID found that fully satisfies requirements
key has issues key_size_2048

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	8206 A196 2084 7E6D 0DF8 B176 BC19 6A94 EDDD A1B7
Main key	key_size_2048 (last updated: 2024-12-09 14:12 UTC)
UID أحمد المحمودي (Ahmed El-Mahmoudy) <aelmahmoudy, users.sourceforge.net>	ok, 0 non-DD sigs, 0 DD sigs: none
UID أحمد المحمودي <ahmed.elmahmoudy, ojuba.org>	ok, 0 non-DD sigs, 0 DD sigs: none
UID أحمد المحمودي (Ahmed El-Mahmoudy) <aelmahmoudy, sabily.org>	skip uid_revoked, 0 non-DD sigs, 0 DD sigs: none
UID أحمد المحمودي (Ahmed El-Mahmoudy) <aelmahmoudy, ubuntu.com>	ok, 0 non-DD sigs, 0 DD sigs: none
UID أحمد المحمودي (Ahmed El-Mahmoudy) <aelmahmoudy, opencores.org>	ok, 0 non-DD sigs, 0 DD sigs: none
UID أحمد المحمودي (Ahmed El-Mahmoudy) <aelmahmoudy-guest, users.alioth.debian.org>	ok, 0 non-DD sigs, 0 DD sigs: none
UID أحمد المحمودي (Ahmed El-Mahmoudy) <aelmahmoudy, varkonsemi.com>	skip uid_revoked, 0 non-DD sigs, 0 DD sigs: none
UID أحمد المحمودي (Ahmed El-Mahmoudy) <ahmed.elmahmoudy, wasiela.com>	ok, 0 non-DD sigs, 0 DD sigs: none

Active key endorsements

Endorsed by

Date

Statement

Actions

duck

2023-05-07
(1 year, 7 months ago)

For nm.debian.org, at 2023-05-07:

I have worked with أحمد المحمودي on dico and wikitrans packages since 2010.

Since 2017 I have records of work exchange with أحمد المحمودي using the email address aelmahmoudy@users.sourceforge.net
using a GPG key with fingerprint 8206 A196 2084 7E6D 0DF8  B176 BC19 6A94 EDDD A1B7.

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.

Due to the long-term interactions we had, I'm convinced that أحمد المحمودي as they
present themselves on nm.debian.org is the rightful owner of both email
aelmahmoudy@users.sourceforge.net and GPG key 8206 A196 2084 7E6D 0DF8  B176 BC19 6A94 EDDD A1B7.

\_o<

Signed with key 7297 2A83 E526 453D F288 5F81 55E9 F9F7 AC1C 443F

View raw

Log

Date	Author	Action	Content	Public
2018-09-01 03:16	aelmahmoudy	-	Also I have a new 4096 key (a7ef5761), also signed by Mohammed Sameer, but it isn't on the Debian keyring	yes
2018-09-01 02:29	aelmahmoudy	-	The key has been signed by Moham,ed Sameer's new key (661efe9a). He still needs to get his new key signed by DDs and upload it to the keyring.	yes
2018-08-27 20:38	noodles	-	I have added a note on the consistent use of this key in the Electronics team to the mail archive; numerous uses in mailing lists posts / conversations since September 2010, rather than purely for DM uploads.	yes
2017-10-24 09:06	aelmahmoudy	-	I just checked msameer's entry in the LDAP database, and it lists the A3FD0DF7 key as his active key.	yes
2017-10-14 02:19	aelmahmoudy	-	My key is signed by an old key of Mohammed Sameer (key id: A3FD0DF7) on Aug 5th, 2014	yes