Key consistency checks
This requirement looks incomplete.
- 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
||BB45 B0B3 FF56 1BDB D45E E8A9 B35B 49EA 5D56 3EFE
ok (last updated: 2020-11-29 08:22 UTC)
|UID Stephan Lachnit <stephanlachnit, protonmail.com>
ok, 0 non-DD sigs,
1 DD sigs:
- B01D1A72AC8DC9A1: Jonathan Carter <email@example.com>
Active key endorsements
(1 week, 3 days ago)
For nm.debian.org, at 2021-01-05:
For the past 7 months, I've sponsored the package setzer
(versions 0.2.5-1, 0.3.1-1 and 0.3.4-1), which were prepared by Stephan Lachnit.
For this past work, Stephan Lachnit 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 BB45 B0B3 FF56 1BDB D45E E8A9 B35B 49EA 5D56 3EFE.
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 Stephan Lachnit as they
present themselves on nm.debian.org is the rightful owner of both email
email@example.com and GPG key BB45 B0B3 FF56 1BDB D45E E8A9 B35B 49EA 5D56 3EFE.
Signed with key BBBD 45EA 818A B86F F67E 7285 D3E1 7383 CFA7 FF06
||Please either get another signature on your GPG key from a DD or get your key endorsed by a DD who did not sign your key. :)