• People
  • Site wizard
  • Wiki help
  • ncts
    DDPO Portfolio Contributor
  • Login
  1. Blair Noctis
  2. Debian Developer, uploading
  3. 1199: Key consistency checks

Key consistency checks

This requirement looks incomplete.

This process has been closed by nm@debian.org on 2023-08-22: 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 59D8 4D44 CCD0 E826 47AE DA29 C21D 9AD4 23A3 9727
Main key key_encryption_expires_soon key_signing_expires_soon (last updated: 2025-04-28 23:00 UTC)
UID Blair Noctis <ncts, nightsail.net> ok, 0 non-DD sigs, 0 DD sigs:
  • none
UID Blair Noctis <keyholding, ncts.me> ok, 0 non-DD sigs, 0 DD sigs:
  • none
UID Blair Noctis <keyholding, noctis.im> skip uid_revoked, 0 non-DD sigs, 0 DD sigs:
  • none
UID Blair Noctis <n, sail.ng> ok, 0 non-DD sigs, 1 DD sigs:
  • 2C7C3146C1A00121: Jonas Smedegaard <dr@jones.dk>
UID Blair Noctis <me, noctis.im> skip uid_revoked, 0 non-DD sigs, 0 DD sigs:
  • none
UID Blair Noctis <code, noctis.im> skip uid_revoked, 0 non-DD sigs, 0 DD sigs:
  • none
UID Blair Noctis (Code Signing) <code, noctis.im> skip uid_revoked, 0 non-DD sigs, 0 DD sigs:
  • none
UID Blair Noctis <ncts, debian.org> ok, 0 non-DD sigs, 0 DD sigs:
  • none

Active key endorsements

Endorsed by Date Statement Actions
jamessan 2024-07-06
(10 months, 1 week ago)
For nm.debian.org, at 2024-07-06:
For the past ~1.5 years, I have worked with Blair Noctis in the pkg-rust team.

For this past work, Blair Noctis sent mails using the email address n@sail.ng
which is the one they're using on nm.debian.org, and they signed their work and
email using a GPG key with fingerprint 59D8 4D44 CCD0 E826 47AE  DA29 C21D 9AD4 23A3 9727.

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 Blair Noctis as they
present themselves on nm.debian.org is the rightful owner of both email
n@sail.ng and GPG key 59D8 4D44 CCD0 E826 47AE  DA29 C21D 9AD4 23A3 9727.
Signed with key 91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
View raw
js 2022-11-22
(2 years, 5 months ago)
For nm.debian.org, at 2022-11-22:
For the past 2-3 months, I have worked with Blair Noctis on sccache and
other Rust-related packages.

For this past work, Blair Noctis sent mails using the email address
n@sail.ng which is the one they're using on nm.debian.org, and they
signed their work and email using a GPG key with fingerprint
59D8 4D44 CCD0 E826 47AE  DA29 C21D 9AD4 23A3 9727.

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 Blair Noctis
as they present themselves on nm.debian.org is the rightful owner of both
email n@sail.ng and GPG key
59D8 4D44 CCD0 E826 47AE  DA29 C21D 9AD4 23A3 9727.
Signed with key 9FE3 E9C3 6691 A69F F53C C684 2C7C 3146 C1A0 0121
View raw

Log

Date Author Action Content Public

Copyright © 2012--2020 Debian Front Desk. Source code is available on Salsa. Report bugs on Salsa or the Debian BTS.

This page is also available in the following languages: , , , ,