Key consistency checks

This requirement looks incomplete.

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, or an Eliptic Curve based key
the key should have the sign, certify and encrypt capabilities (subkeys are encouraged)
for an RSA key, the primary cryptographic material should be at least 4096 bits
the UIDs used by an applicant to work in the project should be signed (certified) 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	6E1E E214 2DDD 3ECE 2F66 6737 7078 CC05 8104 504F
Main key	ok (last updated: 2026-06-02 19:19 UTC)
UID Seyed Mohamad Amin Modaresi <modaresisofthard, proton.me>	ok, 0 non-DD sigs, 0 DD sigs: none

Active key endorsements

Endorsed by

Date

Statement

Actions

eamanu

2026-06-02
(2 weeks, 6 days ago)

For nm.debian.org, at 2026-06-02: For the past 7 months, I have worked with
Seyed Mohamad Amin Modaresi on python-asciimatics, python-generic,
pyhton-graphs, python3-pytesseract, planify and Bazaar.

For this past work, Seyed Mohamad Amin Modaresi sent mails using the email
address modaresisofthard@proton.me which is the one they're using on
nm.debian.org, and they signed their work and email using a GPG key with
fingerprint 6E1E E214 2DDD 3ECE 2F66 6737 7078 CC05 8104 504F. Examples of those
mails and contributions signed with that key are visible here
https://salsa.debian.org/amin_modaresi.gpg.

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 Seyed Mohamad Amin
Modaresi as they present themselves on nm.debian.org is the rightful owner of
both email modaresisofthard@proton.me and GPG key 6E1E E214 2DDD 3ECE 2F66 6737
7078 CC05 8104 504F.

Signed with key 1379 6755 BBC7 2BB8 ABE2 AEB5 FA9D EC5D E11C 63F1

View raw

Log

Date	Author	Action	Content	Public