Key consistency checks

This requirement has been approved by Pierre-Elliott Bécue <peb@debian.org> 11 months, 3 weeks ago.

This process has been closed by peb on 2024-07-08: no further modifications are possible.

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	D017 9263 E202 0E40 7157 4073 A5FF 4BB3 EA53 C5DF
Main key	ok (last updated: 2024-12-20 15:49 UTC)
UID Vivek K J <vivekkj, disroot.org>	ok, 0 non-DD sigs, 3 DD sigs: B3F5945285219E1F: Mohammed Bilal <mdbilal@disroot.org> 8F53E0193B294B75: Praveen Arimbrathodiyil (Pirate) <praveen@onenetbeyond.org> 863D4DF2ED9C28EF: Abhijith PA <abhijith@disroot.org>
UID Vivek K J <vivekkj, tchncs.de>	ok, 0 non-DD sigs, 3 DD sigs: B3F5945285219E1F: Mohammed Bilal <mdbilal@disroot.org> 8F53E0193B294B75: Praveen Arimbrathodiyil (Pirate) <praveen@onenetbeyond.org> 863D4DF2ED9C28EF: Abhijith PA <abhijith@disroot.org>
UID Vivek K J <vivekkj2004, gmail.com>	ok, 0 non-DD sigs, 3 DD sigs: B3F5945285219E1F: Mohammed Bilal <mdbilal@disroot.org> 8F53E0193B294B75: Praveen Arimbrathodiyil (Pirate) <praveen@onenetbeyond.org> 863D4DF2ED9C28EF: Abhijith PA <abhijith@disroot.org>

Active key endorsements

Endorsed by

Date

Statement

Actions

praveen

2022-08-24
(2 years, 4 months ago)

For nm.debian.org, at 2022-08-24:
For the past many months, I have worked with Vivek K J on ruby gem packages.

For this past work, for last one moneht, Vivek K J sent mails using the email
address vivekkj@disroot.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
D017 9263 E202 0E40 7157  4073 A5FF 4BB3 EA53 C5DF.

Before this he was using <vivekkj@protonmail.com> and key
184CC5F4856495978CD5E78F93AE9C793ED11852 since only paid version of protonmail
provides smtp access, he could not sign mails using a gpg supported client, so
he switched his email address to disroot.org which provides smtp access. Due to
this change he had to close his earlier process and start again with this new
process.

Additionally we have been interacting over matrix all this time in addition to
communication over email.

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 Vivek K J as they
present themselves on nm.debian.org is the rightful owner of both email
vivekkj@disroot.org and GPG key D017 9263 E202 0E40 7157  4073 A5FF 4BB3 EA53 C5DF.

Signed with key D308 63E2 6020 E543 F471 9A83 8F53 E019 3B29 4B75

View raw

Log

Date	Author	Action	Content	Public
2024-01-03 12:07	peb	req_approve	Requirement approved	yes