Key consistency checks

This requirement looks incomplete.

This process has been closed by peb on 2024-07-08: 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	70A0 AC45 AC77 9EFE 84F6 3AED 724A A9B5 2F02 4C8B
Main key	ok (last updated: 2024-12-06 08:19 UTC)
UID Phil Wyett (Playing the game for the games sake.) <philip.wyett, kathenas.org>	ok, 0 non-DD sigs, 0 DD sigs: none

Active key endorsements

Endorsed by

Date

Statement

Actions

bage

2024-12-17
(1 week, 2 days ago)

For nm.debian.org, at 2024-12-17:
For the past 3 years, I have worked with Philip Wyett on filezilla,
libfilezilla, w-scan-cpp, vdr-plugin-wirbelscan, compton, and rednotebook.

For this past work, Philip Wyett sent mails using the email address philip.wyett@kathenas.org
which is the one he is using on nm.debian.org, and he has signed his work and
email using a GPG key with fingerprint 70A0 AC45 AC77 9EFE 84F6  3AED 724A A9B5 2F02 4C8B.

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'm convinced that Philip Wyett as he
presents himself on nm.debian.org is the rightful owner of both email
philip.wyett@kathenas.org and GPG key 70A0 AC45 AC77 9EFE 84F6  3AED 724A A9B5 2F02 4C8B.

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

View raw

kilobyte

2022-03-18
(2 years, 9 months ago)

For nm.debian.org, at 2022-03-18:
I have sponsored a good number of packages by Philip Wyett, and the only key
matching his name in my keyring is 70A0AC45AC779EFE84F63AED724AA9B52F024C8B.
I am thus sure that this key has been used to sign recent uploads to
mentors.debian.net, and those uploads have passed my review, thus ensuring
that whoever controls that key is capable of doing good Debian work.

I have not checked if that person carries an officially-looking id with a
badly made photo, which used to be the sole concern for key signing -- but
that's not what I'm hereby certifying.

This key has been in my keyring since before 2021-01-01 (I've just checked
yearly backup from that date).

Signed with key FD9C E2D8 D775 4B78 AB27 9BBD 2C3B 436F EAC6 8101

View raw

Log

Date	Author	Action	Content	Public