Key consistency checks
requirement has been approved by Jonathan McDowell <email@example.com>
2 months, 1 week ago.
process has been closed by noodles on
2021-03-23: no further modifications are possible.
- 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
||506C 15A4 2B0A F5A0 A854 23EE D28A 45BF 3287 D649
ok (last updated: 2021-04-10 09:35 UTC)
|UID Mark Hindley <leepen, debian.org>
ok, 0 non-DD sigs,
0 DD sigs:
|UID Mark Hindley <mark, hindley.org.uk>
ok, 0 non-DD sigs,
0 DD sigs:
Active key endorsements
(2 months, 2 weeks ago)
For nm.debian.org, at 2021-01-29:
I have been in touch with Mark since roughly 2007, he took over my apt-cacher package.
The earliest use of the key
506C 15A4 2B0A F5A0 A854 23EE D28A 45BF 3287 D649
known to me was in a conversation in 2017, I can verify the signature of that message in my mail archive without any issue, it appears to be the same key.
I can confirm that we can communicate in encrypted way using his private key which was bundled with the key aforementioned key received back then.
Due to the long-term interactions we had, I'm convinced that Mark Hindley as he
present himself on nm.debian.org is the rightful owner of both email
firstname.lastname@example.org and GPG key 506C 15A4 2B0A F5A0 A854 23EE D28A 45BF 3287 D649.
Signed with key 648D D98F 4BC4 8290 17CB 0E34 6974 0E5C B35F EC3C
(2 months, 3 weeks ago)
For nm.debian.org, at 2021-01-20:
For the past 9 months, I have worked with Mark Hindley on matters
relating to the support of alternative init systems in Debian.
For this past work, Mark Hindley sent mails using the email address
email@example.com which is the one they're using on nm.debian.org,
and they signed their work and email using a GPG key with fingerprint
506C 15A4 2B0A F5A0 A854 23EE D28A 45BF 3287 D649.
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 Mark
Hindley as they present themselves on nm.debian.org is the rightful
owner of both email firstname.lastname@example.org and
GPG key 506C 15A4 2B0A F5A0 A854 23EE D28A 45BF 3287 D649.
Signed by: Matthew Vernon <email@example.com>
Signed with key BA4E F9C8 4DF9 6D37 D8A1 E2D4 12F4 D21C 8F6A 63C8
||One key endorsement is not enough to proceed. Do you have plans to get a regular signature on your key, or more endorsements?