Key consistency checks

This requirement has been approved by Pierre-Elliott Bécue <peb@debian.org> 2 years, 2 months ago.

This process has been closed by johns on 2023-02-26: no further modifications are possible.

Potential problems

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

OpenPGP fingerprint	23EB CF7E 8FC4 7556 7871 00DF A425 4072 E373 042C
Main key	ok (last updated: 2024-11-11 05:31 UTC)
UID Jakub Ružička <jru, debian.org>	ok, 0 non-DD sigs, 0 DD sigs: none
UID Jakub Ružička (packaging) <jakub.ruzicka, nic.cz>	ok, 0 non-DD sigs, 1 DD sigs: E8446B4AC8C77261: Andrej Shadura <andrew@shadura.me>

Active key endorsements

Endorsed by

Date

Statement

Actions

santiago

2022-09-12
(2 years, 2 months ago)

For nm.debian.org, at 2022-09-12:
I have worked with Jakub Ružička since early November 2020 on lua-binaryheap
(#974080), knot, knot-resolver among other packages.

For this past work, Jakub Ružička sent mails using the email address
jakub.ruzicka@nic.cz which is the one he is using on nm.debian.org, and Jakub
signed his work and email using a GPG key with fingerprint
23EB CF7E 8FC4 7556 7871  00DF A425 4072 E373 042C.

Jakub also uses to sign his git commits/tags in the
repositories of the above mentioned packages, using his key. E.g.:
https://salsa.debian.org/jruzicka/lua-binaryheap/-/commit/d4fa1e41c3e35b63bc1d80d2ce5ded5306cbaade
https://salsa.debian.org/dns-team/knot-dns/-/commit/81517b939c0d4539732ef426358d44ba25aa3f2f
https://salsa.debian.org/dns-team/knot-resolver/-/commit/f92519d8b5baae5e1038af445435880c8ef00af8
and more recently:
https://salsa.debian.org/dns-team/knot-dns/-/tree/debian/3.2.0-3

I've made sure that Jakub is able to decrypt encrypted messages sent to this
key and that he is able to sign messages with the same key.
This public mail (from 26 Aug 2021) has also been signed by Jakub:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991463#35

Due to the interactions we had since November 2020, I'm convinced that Jakub
Ružička, as his present himself on nm.debian.org, is the rightful owner of both
email jakub.ruzicka@nic.cz and GPG key
23EB CF7E 8FC4 7556 7871  00DF A425 4072 E373 042C.

Signed with key A2FD 948D 3153 DC84 1A3E 6C89 22AF D1C0 DAC8 BC06

View raw

edmonds

2021-04-06
(3 years, 7 months ago)

For nm.debian.org, on 2021-04-06:

Since late 2020, I have worked with Jakub Ružička reviewing changes to several
Debian packages, including knot and knot-resolver.

For this past work, Jakub Ružička sent mails using the email address jakub.ruzicka@nic.cz
which is the one they're using on nm.debian.org, and they signed their work and
email using a GPG key with fingerprint 23EB CF7E 8FC4 7556 7871  00DF A425 4072 E373 042C.

Due to the long-term interactions we had, I'm convinced that Jakub Ružička as they
present themselves on nm.debian.org is the rightful owner of both email
jakub.ruzicka@nic.cz and GPG key 23EB CF7E 8FC4 7556 7871  00DF A425 4072 E373 042C.

Signed with key DF3D 96EE B382 7820 F302 665C 0181 7AB0 AAF6 CDAE

View raw

santiago

2021-03-25
(3 years, 8 months ago)

For nm.debian.org, at 2021-03-25:
I have worked with Jakub Ružička since early November 2020 on lua-binaryheap
(#974080), knot and knot-resolver.

For this past work, Jakub Ružička sent mails using the email address
jakub.ruzicka@nic.cz which is the one he is using on nm.debian.org, and Jakub
signed his work and email using a GPG key with fingerprint
23EB CF7E 8FC4 7556 7871  00DF A425 4072 E373 042C.

Jakub has also signed several commits (most of his commits, I think) in the
repositories of the above mentioned packages using his key. E.g.:
https://salsa.debian.org/jruzicka/lua-binaryheap/-/commit/d4fa1e41c3e35b63bc1d80d2ce5ded5306cbaade
https://salsa.debian.org/dns-team/knot-dns/-/commit/81517b939c0d4539732ef426358d44ba25aa3f2f
https://salsa.debian.org/dns-team/knot-resolver/-/commit/f92519d8b5baae5e1038af445435880c8ef00af8

I've made sure that Jakub is able to decrypt encrypted messages sent to this
key and that he is able to sign messages with the same key.

Due to the interactions we had since November 2020, I'm convinced that Jakub
Ružička, as his present himself on nm.debian.org, is the rightful owner of both
email jakub.ruzicka@nic.cz and GPG key
23EB CF7E 8FC4 7556 7871  00DF A425 4072 E373 042C.

Signed with key A2FD 948D 3153 DC84 1A3E 6C89 22AF D1C0 DAC8 BC06

View raw

Log

Date	Author	Action	Content	Public
2022-09-12 22:17	peb	req_approve	Requirement approved	yes