Key consistency checks

This requirement has been approved by Mattia Rizzolo <mattia@debian.org> 3 years, 4 months ago.

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

Potential problems

key has issues key_encryption_expires_soon key_signing_expires_soon

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	B153 481D B739 CC87 A3D6 5DCF 0620 23CA 3E06 BDD5
Main key	key_encryption_expires_soon key_signing_expires_soon (last updated: 2025-05-12 02:35 UTC)
UID Peymaneh <peymaneh, posteo.net>	ok, 0 non-DD sigs, 2 DD sigs: 5262E7FF491049FE: Jonas Meurer <jonas@freesources.org> EA2DB6963F8B2984: Georg Faerber <georg@riseup.net>

Active key endorsements

Endorsed by

Date

Statement

Actions

mejo

2021-12-16
(3 years, 4 months ago)

For nm.debian.org, at 2021-12-16:
For the past year or so, I have worked with Peymaneh on packaging caddy, amongh
other things.

For this past work, Peymaneh sent mails using the email address peymaneh@posteo.net
which is the one they're using on nm.debian.org, and they signed their work and
email using a GPG key with fingerprint B153 481D B739 CC87 A3D6  5DCF 0620 23CA 3E06 BDD5.

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 Peymaneh as they
present themselves on nm.debian.org is the rightful owner of both email
peymaneh@posteo.net and GPG key B153 481D B739 CC87 A3D6  5DCF 0620 23CA 3E06 BDD5.

Signed with key 2C8C D283 D3EF DF43 3890 E783 5262 E7FF 4910 49FE

View raw

Log

Date	Author	Action	Content	Public
2021-12-19 15:30	mattia	req_approve	Requirement approved	yes
2021-12-19 12:23	peymaneh	-	Hi Santiago. I uploaded my key with DD signature ubuntu keyserver. Took me some days since to realize I have to refresh the state of my public key on nm.debian.org myself... 😅	yes
2021-12-08 10:43	santiago	-	Hello Peymaneh. As I told you in your first application (https://nm.debian.org/process/926/), your key still needs to be signed or strongly endorsed. What are your plans for that? Best, -- Santiago	yes