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
||688D CAA6 B9C9 D63F 6AD4 B1DF 64C7 0881 4523 D373
ok (last updated: 2021-09-10 10:19 UTC)
|UID Nkwuda Sunday Cletus (signing key) <sonnietech, disroot.org>
ok, 0 non-DD sigs,
0 DD sigs:
|UID Nkwuda Sunday Cletus (git gpg key) <scletus40, yahoo.com>
ok, 0 non-DD sigs,
0 DD sigs:
Active key endorsements
(1 week ago)
For nm.debian.org, at 2021-09-12:
as part of Outreachy.
For this past work, Nkwuda Sunday Cletus sent mails using the email address firstname.lastname@example.org
and recently started using 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
688D CAA6 B9C9 D63F 6AD4 B1DF 64C7 0881 4523 D373. Additionally we have been interacting over matrix
all through out the outreachy internship period using @sonnie:matrix.org They been signing commits
using the same gpg key and I cross verified the email change and encryption via matrix chat.
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 (I confirmed this using matrix chat).
Due to the long-term interactions we had, I'm convinced that Nkwuda Sunday Cletus as they
present themselves on nm.debian.org is the rightful owner of both email
firstname.lastname@example.org and GPG key 688D CAA6 B9C9 D63F 6AD4 B1DF 64C7 0881 4523 D373.
Signed with key D308 63E2 6020 E543 F471 9A83 8F53 E019 3B29 4B75
Thanks for your interest. However for your process to pass the Key Consistency checks you'll need at least one Debian Member to sign your GPG key or one endorsement.
With best regards,