Key consistency checks

This requirement has been approved by Jonathan McDowell <noodles@earth.li> 1 year, 11 months ago.

This process has been closed by noodles on 2022-10-09: 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 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	3465 469C B19D 61E5 E2EA 8AFB EF24 2F70 9F91 2FBE
Main key	ok (last updated: 2024-08-26 04:22 UTC)
UID Taavi Väänänen <hi, taavi.wtf>	ok, 0 non-DD sigs, 2 DD sigs: 68E713981D1515F8: Arturo Borrero Gonzalez <arturo@debian.org> 52FC8E7BEDB7FCA2: Kunal Mehta <legoktm@riseup.net>
UID Taavi Väänänen <taavi, helsec.fi>	ok, 0 non-DD sigs, 2 DD sigs: 68E713981D1515F8: Arturo Borrero Gonzalez <arturo@debian.org> 52FC8E7BEDB7FCA2: Kunal Mehta <legoktm@riseup.net>
UID Taavi Väänänen <taavi, debian.org>	ok, 0 non-DD sigs, 0 DD sigs: none
UID Taavi Väänänen <taavi, majava.org>	ok, 0 non-DD sigs, 0 DD sigs: none

Active key endorsements

Endorsed by

Date

Statement

Actions

arturo

2022-10-04
(1 year, 11 months ago)

For nm.debian.org, at 2022-10-04:
For the past couple years, I have worked with Taavi Väänänen on several open source projects.

For this past work, Taavi Väänänen sent mails using the email address hi@taavi.wtf
which is the one they're using on nm.debian.org, and they signed their work and
email using a GPG key with fingerprint 3465 469C B19D 61E5 E2EA  8AFB EF24 2F70 9F91 2FBE.

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 Taavi Väänänen as they
present themselves on nm.debian.org is the rightful owner of both email
hi@taavi.wtf and GPG key 3465 469C B19D 61E5 E2EA  8AFB EF24 2F70 9F91 2FBE.

Signed with key DD98 61AB 23DC 3333 892E 07A9 68E7 1398 1D15 15F8

View raw

legoktm

2022-10-04
(1 year, 11 months ago)

For nm.debian.org, at 2022-10-04:
For the past 2+ years, I have worked with Taavi Väänänen on MediaWiki packaging
plus general Wikimedia development.

For this past work, Taavi Väänänen sent mails using the email address hi@taavi.wtf
which is the one they're using on nm.debian.org, and they signed their work and
email using a GPG key with fingerprint 3465 469C B19D 61E5 E2EA  8AFB EF24 2F70 9F91 2FBE.

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 Taavi Väänänen as they
present themselves on nm.debian.org is the rightful owner of both email
hi@taavi.wtf and GPG key 3465 469C B19D 61E5 E2EA  8AFB EF24 2F70 9F91 2FBE.

Signed with key FA1E 9F9A 41E7 F435 02CA 5D63 52FC 8E7B EDB7 FCA2

View raw

Log

Date	Author	Action	Content	Public
2022-10-08 16:05	noodles	req_approve	Requirement approved	yes