Key consistency checks

This requirement has been approved by Mattia Rizzolo <mattia@debian.org> 3 years, 4 months ago.

This process has been closed by noodles on 2021-11-12: 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	803C E41F 4DC2 52EC B5E5 F1B9 D12B 2BE2 6D3F F663
Main key	ok (last updated: 2025-01-29 11:47 UTC)
UID Doug Torrance <dtorrance, debian.org>	ok, 0 non-DD sigs, 0 DD sigs: none
UID Doug Torrance <dtorrance, piedmont.edu>	ok, 0 non-DD sigs, 0 DD sigs: none
UID Doug Torrance <dtorrance, monmouthcollege.edu>	skip uid_revoked, 0 non-DD sigs, 0 DD sigs: none

Active key endorsements

Endorsed by

Date

Statement

Actions

ametzler

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

Hello,

I have been interacting with Dough in the wmaker team, I am the long
term-sponsor there. I have uploaded packages as commited to salsa, so the GIT
repositories there are the main way of communication, with an occassional
"please upload"-mail.

I did the following checks for his key:
- - Verify he can decrypt mails encrypted with the key and sent to 
  dtorrance@piedmont.edu
- - Checked Git commits of uploads of wmaker related packages that I had
  sponsored for signed commmits. Recent commits are signed with respective
  key.

Since salsa considers the respective commits "verified" I am confident that
dtorrance on salsa controls the key, so I can endorse it.

cu Andreas

Signed with key D2E0 9203 9EF8 D496 EDF4 FA5E A54F 0185 4382 1484

View raw

nilesh

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

I been interacting with and have been regularly seeing Douglas Andrew Torrance's emails
to debian science ever since I joined in the team - which amounts to
around an year or so earlier.
Since then I've seen them doing high quality work, and interactions with Douglas have always been constructive

Recently, they joined in the R package team and I sponsored a couple
uploads for them - all perfect.

I did the following checks for their keys:

1. Checked recent mails
2. Checked all recent commits on salsa
These have been signed with their subkey: "BA9821C12E07894FB2E4AD0091DC4A779EC5C910"

3. I have made sure they are able to decrypt messages sent to them with
the key 803CE41F4DC252ECB5E5F1B9D12B2BE26D3FF663

Due to past interactions with Douglas, and the checks made mentioned above,
I'm convinced that Douglas Andrew Torrance is indeed the owner of both email
dtorrance@piedmont.edu and GPG key "803C E41F 4DC2 52EC B5E5  F1B9 D12B 2BE2 6D3F F663"

Douglas has been contributing to the project for around 8 years by now, and I'd be very happy if
the signature endorsment helps their application proceed forward

Signed with key 3E99 A526 F5DC C0CB BF1C EEA6 00BA E74B 3433 69F1

View raw

Log

Date	Author	Action	Content	Public
2021-09-30 09:46	mattia	req_approve	Requirement approved	yes