Key consistency checks

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

This process has been closed by johns on 2024-01-20: 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	70A4 7058 E225 C1A8 9FE3 B448 2D48 F45A 7EBE 8C12
Main key	ok (last updated: 2025-01-08 06:04 UTC)
UID Soren Stoutner <soren, debian.org>	ok, 0 non-DD sigs, 0 DD sigs: none
UID Soren Stoutner <soren, stoutner.com>	ok, 0 non-DD sigs, 1 DD sigs: 0F56D0553B6D411B: Sean Whitton <spwhitton@spwhitton.name>

Active key endorsements

Endorsed by

Date

Statement

Actions

mitya57

2023-11-23
(1 year, 1 month ago)

Since the beginning of 2023, I have worked with Soren Stoutner on privacybrowser
and qtwebengine-opensource-src.

For this past work, Soren Stoutner sent mails using the email address soren@stoutner.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 70A4 7058 E225 C1A8 9FE3  B448 2D48 F45A 7EBE 8C12.

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 Soren Stoutner as they
present themselves on nm.debian.org is the rightful owner of both email
soren@stoutner.com and GPG key 70A4 7058 E225 C1A8 9FE3  B448 2D48 F45A 7EBE 8C12.

Signed with key F242 99FF 1BBC 9018 B906 A4CB 6026 936D 2F1C 8AE0

View raw

bage

2023-11-22
(1 year, 1 month ago)

For nm.debian.org, at 2023-11-22:
For the first half of the past year, I have worked with Soren Stoutner on electrum.

For this past work, Soren Stoutner sent mails using the email address soren@stoutner.com
which is the one he uses on nm.debian.org, and he signed his work and email using a GPG
key with fingerprint 70A4 7058 E225 C1A8 9FE3  B448 2D48 F45A 7EBE 8C12.

I've made sure that he 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 long-term interactions we had, I am convinced that Soren Stoutner as he
presents himself on nm.debian.org is the rightful owner of both email
soren@stoutner.com and GPG key 70A4 7058 E225 C1A8 9FE3  B448 2D48 F45A 7EBE 8C12.

Signed with key 2861 2573 17C7 AEE4 F880 497E C386 0AC5 9F57 4E3A

View raw

Log

Date	Author	Action	Content	Public
2023-11-26 16:38	noodles	req_approve	Requirement approved	yes