Key consistency checks
requirement has been approved by Jonathan McDowell <firstname.lastname@example.org>
2 weeks, 1 day ago.
process has been approved by santiago on
2023-01-31: 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
||11C6 2C63 4CC6 1C07 74A7 EE12 2C51 41A1 5285 EC0A
ok (last updated: 2023-01-22 13:06 UTC)
|UID Vasyl Gello <vasek.gello, gmail.com>
ok, 1 non-DD sigs,
0 DD sigs:
Active key endorsements
(2 months, 2 weeks ago)
For nm.debian.org, at 2022-11-20
For the past 2 years, I have worked with Vasyl Gello on kodi packaging.
For this past work, Vasyl Gello 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 (I'm talking git commits as well as signed
tarballs) using a GPG key with fingerprint
11C6 2C63 4CC6 1C07 74A7 EE12 2C51 41A1 5285 EC0A.
He also has done that very consistently, though I haven't seen many
gpg-signed mails, all his git commits and tags have been signed.
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 Vasyl Gello as they
present themselves on nm.debian.org is the rightful owner of both email
firstname.lastname@example.org and GPG key 11C6 2C63 4CC6 1C07 74A7 EE12 2C51 41A1 5285 EC0A.
Signed with key 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540