Key consistency checks

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

This process has been closed by johns on 2023-08-21: 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	D622 3890 E7C4 625B 2C14 68D1 AB18 1FDB 41DD 41C4
Main key	ok (last updated: 2024-12-06 19:08 UTC)
UID John Scott <jscott, posteo.net>	ok, 0 non-DD sigs, 0 DD sigs: none
UID jscott, posteo.net	ok, 0 non-DD sigs, 0 DD sigs: none
UID John Scott	ok, 1 non-DD sigs, 0 DD sigs: none

Active key endorsements

Endorsed by

Date

Statement

Actions

glaubitz

2023-08-16
(1 year, 4 months ago)

For nm.debian.org, at 2023-08-15:
I support John Scott <jscott@posteo.net>'s request to become Debian Maintainer.
I have reviewed and sponsored John's packages revolving around software for
embedded systems and electronics in Debian since at least 2021.

Since John's efforts cover the SuperH architecture, I have been particularly
interested to support his work since I am not only Debian's primary maintainer
of the unofficial SuperH port (called "sh4 in Debian) but also the maintainer
of the SuperH port in the upstream kernel.

With John joining the project as a Debian Maintainer, there will be another
developer doing SuperH work in Debian which might help to fully revive the port
in the future on upcoming J-Core hardware, an open-source clone of the SuperH
architecture.

While I have not met John in person, I am confident that due to the long-term
interactions I have had with him, he is the rightful owner of the email address
jscott@posteo.net and GPG key D622 3890 E7C4 625B 2C14  68D1 AB18 1FDB 41DD 41C4.

Signed with key 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913

View raw

bage

2023-08-11
(1 year, 4 months ago)

For nm.debian.org, at 2023-08-11:
For the past 15 months, I have worked with John Scott on binutils-sh-elf, gcc-sh-elf,
open-ath9k-htc-firmware, and the ITP for carl9170fw.

For this past work, John Scott sent mails using the email address jscott@posteo.net
which is the one he uses on nm.debian.org, and he signed his work and email using a
GPG key with fingerprint D622 3890 E7C4 625B 2C14  68D1 AB18 1FDB 41DD 41C4.

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 John Scott as they
present themselves on nm.debian.org is the rightful owner of both email
jscott@posteo.net and GPG key D622 3890 E7C4 625B 2C14  68D1 AB18 1FDB 41DD 41C4.

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

View raw

Log

Date	Author	Action	Content	Public
2023-08-17 17:31	noodles	req_approve	Requirement approved	yes