Key consistency checks

This requirement has been approved by Santiago Ruano Rincón <santiagorr@riseup.net> 1 week, 5 days ago.

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	2D65 BC1E B966 5A6E 97F9 730A B3F5 9452 8521 9E1F
Main key	ok (last updated: 2023-03-10 17:15 UTC)
UID Mohammed Bilal <mdbilal, disroot.org>	ok, 0 non-DD sigs, 1 DD sigs: 8F53E0193B294B75: Praveen Arimbrathodiyil (Pirate) <praveen@onenetbeyond.org>
UID Mohammed Bilal <rmb, envs.net>	ok, 0 non-DD sigs, 2 DD sigs: 4BCD0567C296D05D: Daniel Leidert <dleidert@debian.org> 8F53E0193B294B75: Praveen Arimbrathodiyil (Pirate) <praveen@onenetbeyond.org>

Active key endorsements

Endorsed by

Date

Statement

Actions

nilesh

2022-04-13
(11 months, 2 weeks ago)

For nm.debian.org, at 2022-04-13:
For the past month, I have worked with Mohammed Bilal on QA work and autopkgtest for
debian med packages. Prior to that I have also seen mails from them on the debian-ruby
mailing list.

For all past work, Mohammed Bilal sent mails using the email address mdbilal@disroot.org
which is the one they're using on nm.debian.org.

I made the following checks on their keys:

- - Checked gpg signature on email, both in personal correspondence and on
  mailing lists which is the same as their key used on nm.d.o
- - Checked signed commits from them indicating good signatures
- - Made sure that they are able to decrypt messages encrypted with their
  GPG key B3F5945285219E1F

Due to the past interactions we had, I'm convinced that Mohammed Bilal as they
present themselves on nm.debian.org is the rightful owner of both email
mdbilal@disroot.org and GPG key 2D65 BC1E B966 5A6E 97F9  730A B3F5 9452 8521 9E1F.

Signed with key 3E99 A526 F5DC C0CB BF1C EEA6 00BA E74B 3433 69F1

View raw

praveen

2022-04-13
(11 months, 2 weeks ago)

For nm.debian.org, at 2022-04-12:
For the past 6+ months, I have worked with Mohammed Bilal in ruby team, libgit2
transition and puma security update.

For this past work, Mohammed Bilal sent mails using the email address mdbilal@disroot.org
which is the one they're using on nm.debian.org, and they signed their work using a GPG key
with fingerprint 2D65 BC1E B966 5A6E 97F9  730A B3F5 9452 8521 9E1F (salsa.debian.org
shows their commits as verified - by matching verified email and key).

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 Mohammed Bilal as they
present themselves on nm.debian.org is the rightful owner of both email
mdbilal@disroot.org and GPG key 2D65 BC1E B966 5A6E 97F9  730A B3F5 9452 8521 9E1F.

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

View raw

Log

Date	Author	Action	Content	Public
2023-03-11 15:59	santiago	req_approve	Requirement approved	yes