Key consistency checks
requirement has been approved by Santiago Ruano Rincón <firstname.lastname@example.org>
2 years, 3 months ago.
process has been closed by gwolf on
2018-04-11: no further modifications are possible.
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 should be signed by at least two existing Debian members (1 for DM applications)
- 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.
This check will be approved manually by Front Desk as the application progresses.
Key check results
||C985 A104 860E 5F2D 2FD8 E8C3 F7D3 FAD9 3328 6674
ok (last updated: 2020-07-01 10:33 UTC)
|UID Bjorn Dolk <debian, bjorndolk.com>
ok, 0 non-DD sigs,
1 DD sigs:
- AFF1D4BDB69135D0: Mikael Djurfeldt <email@example.com>
|UID Bjorn Dolk <dolk, debian.org>
skip uid_revoked, 0 non-DD sigs,
0 DD sigs:
||A new key will not invalidate the existing advocate statement.
||Your statement regarding the key and UID is true. I will work on providing a new key with trust attached to it. This may take a while. Will this also invalidate the advocate statement? I assume it will.
||As far as I can tell the firstname.lastname@example.org uid present on this key has never been valid; this is not a case of a returning DD, but instead someone who is applying for DM status and has never had a Debian email address. Unable to approve this key as a result.