Key consistency checks

This requirement looks incomplete.

This process has been closed by nm@debian.org on 2021-01-29: no further modifications are possible.

Potential problems

no UID found that fully satisfies requirements
key has issues key_encryption_expires_soon key_signing_expires_soon

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	8EC0 3CE5 78AA CDD4 0356 AEE2 CCF9 03D8 6BBE ED0C
Main key	key_encryption_expires_soon key_signing_expires_soon (last updated: 2025-03-03 00:04 UTC)
UID Glenn Strauss (debian) <gstrauss, gluelogic.com>	ok, 0 non-DD sigs, 0 DD sigs: none

Active key endorsements

Endorsed by

Date

Statement

Actions

helmutg

2021-01-21
(4 years, 1 month ago)

For nm.debian.org, at 2021-01-21:

For the past two years, I have worked with Glenn Strauss on lighttpd.

Glenn is the primary upstream author of lighttpd. He signed all recent upstream
releases with a different key whose fingerprint is:

    649D 0DD7 67FF 2062 02A7 6C51 58F1 4A78 6FE1 98C8

I've verified those signatures for all uploads that I made to Debian in the
lighttpd package.

With the abovementioned upstream key, Glenn sent me a signed transition
statement endorsing his new key for Debian: 

    8EC0 3CE5 78AA CDD4 0356  AEE2 CCF9 03D8 6BBE ED0C

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 interactions during the past two years we had, I'm convinced that
Glenn Strauss as he presents himself on nm.debian.org is the rightful owner of
both email gstrauss@gluelogic.com (the one on the key, not
gs-debian.org@gluelogic.com, but it seems like Glenn is in control of the whole
domain and uses local parts for sorting), GPG key 649D 0DD7 67FF 2062 02A7 6C51
58F1 4A78 6FE1 98C8. Due to the signed transition statement, I'm also convinced
that he is the rightful owner of GPG key 8EC0 3CE5 78AA CDD4 0356 AEE2 CCF9
03D8 6BBE ED0C.

Signed with key 4CC2 D2D9 0A8D 1654 DBF8 73AA 2D1A AACF 2444 4442

View raw

Log

Date	Author	Action	Content	Public
2021-01-07 15:58	peb	-	Your key isn't signed or endorsed by any Debian Developer, you'll have to have it either signed or endorsed by at least two developers.	yes