Key consistency checks
requirement has been approved by Pierre-Elliott Bécue <firstname.lastname@example.org>
6 months ago.
- 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
||DA53 058D BE15 4BDF CBF1 6BAD 4B54 2AF7 04F7 4516
ok (last updated: 2022-03-29 12:56 UTC)
|UID Arun Kumar Pariyar <openarungeek, gmail.com>
ok, 0 non-DD sigs,
1 DD sigs:
- 823E967606C34B96: Utkarsh Gupta <email@example.com>
Active key endorsements
(6 months ago)
For nm.debian.org, at 2022-03-24:
For the past 15 months, I have worked with Arun Kumar Pariyar on various
packages in Deepin team. To give two examples, dde-qt5integration and
For this past work, Arun Kumar Pariyar signed his commits and DM uploads using
a GPG key with fingerprint DA53 058D BE15 4BDF CBF1 6BAD 4B54 2AF7 04F7 4516.
I've made sure that they are able to decrypt messages encrypted with this key
and sent to firstname.lastname@example.org, and to sign messages with the same key.
Due to the long-term interactions we had, I'm convinced that Arun Kumar
Pariyar as they present themselves on nm.debian.org is the rightful owner of
both email email@example.com and GPG key
DA53 058D BE15 4BDF CBF1 6BAD 4B54 2AF7 04F7 4516.
Signed with key F242 99FF 1BBC 9018 B906 A4CB 6026 936D 2F1C 8AE0
(6 months, 1 week ago)
For nm.debian.org, at 2022-03-22:
For the past 2 years, I have worked with Arun Kumar Pariyar on Deepin-related packages within
Debian pkg-deepin packaging team.
For this past work, Arun Kumar Pariyar sent mails using the email address firstname.lastname@example.org
which is the one they're using on nm.debian.org, and they signed their work and
email using a GPG key with fingerprint DA53 058D BE15 4BDF CBF1 6BAD 4B54 2AF7 04F7 4516.
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 Arun Kumar Pariyar as they
present themselves on nm.debian.org is the rightful owner of both email
email@example.com and GPG key DA53 058D BE15 4BDF CBF1 6BAD 4B54 2AF7 04F7 4516.
Signed with key 7E77 2947 6D87 D6F1 1D91 ACCB C293 E7B4 6182 5ACE
(1 year, 10 months ago)
I have seen Arun signing his commits since last month using key
DA53058DBE154BDFCBF16BAD4B542AF704F74516 while working with him in golang team.
Signed with key D308 63E2 6020 E543 F471 9A83 8F53 E019 3B29 4B75