• People
  • Site wizard
  • Wiki help
  • noisycoil
    DDPO Portfolio Contributor
  • Login
  1. NoisyCoil
  2. Debian Maintainer
  3. 1326: Key consistency checks

Key consistency checks

This requirement has been approved by Tiago Bortoletto Vaz <tiago@debian.org> 2 weeks ago.

This process has been closed by johns on 2025-01-17: 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 50CF C9D5 E5BD E1CB CA57 FD7B 6DF0 08E7 0F28 CBF7
Main key ok (last updated: 2025-01-28 09:02 UTC)
UID NoisyCoil <noisycoil, disroot.org> ok, 0 non-DD sigs, 0 DD sigs:
  • none
UID NoisyCoil <noisycoil, tutanota.com> ok, 0 non-DD sigs, 0 DD sigs:
  • none

Active key endorsements

Endorsed by Date Statement Actions
ncts 2024-12-31
(4 weeks ago)		 
For nm.debian.org, at 2024-12-31:
For the past few months, I have worked with NoisyCoil in the Rust team.

They were nice and helpful to work with, and kept a good standard in their
work.

For this past work, NoisyCoil sent mails using the email address
noisycoil@tutanota.com which is the one they're using on nm.debian.org, and
they signed their work and email using a GPG key with fingerprint
50CF C9D5 E5BD E1CB CA57  FD7B 6DF0 08E7 0F28 CBF7.

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 interactions we had, I'm convinced that NoisyCoil, as they present
themselves on nm.debian.org, is the rightful owner of both the email address
and the GPG key listed above.
Signed with key 59D8 4D44 CCD0 E826 47AE DA29 C21D 9AD4 23A3 9727 		View raw
ah 2024-12-20
(1 month, 1 week ago)		 
For nm.debian.org, at 2024-12-20:
For the past several months, I have worked with NoisyCoil on bananas-team and
rust-team on salsa.debian.org.

For this past work, we've mainly interacted via IRC/Matrix and Gitlab
(salsa.debian.org) but NoisyCoil also sent mails using the email address
noisycoil@tutanota.com which is the one they're using on nm.debian.org, and
they signed their work and email using a GPG key with fingerprint
50CF C9D5 E5BD E1CB CA57  FD7B 6DF0 08E7 0F28 CBF7.

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 NoisyCoil as they
present themselves on nm.debian.org is the rightful owner of both email
noisycoil@tutanota.com and GPG key 50CF C9D5 E5BD E1CB CA57  FD7B 6DF0 08E7 0F28 CBF7.
Signed with key FAE1 E5B6 4652 BE79 8E27 8CC2 0BC4 7DC6 4D13 5306 		View raw
werdahias 2024-12-03
(1 month, 3 weeks ago)		 
For nm.debian.org, at 2024-12-03:

For the past 5 months, I have worked with NoisyCoil on various packaging tasks in the Debian Rust team.

They have been packaging some new rust CLI tools, such as broot, du-dust, dysk and procs.
Furthermore, they helped a great deal with some transitions within the team, such as the
bindgen and image transition while preparing others and doing routine updates for other team 
packages.

During my work with noisycoil they were always pleasant to interact with and quickly picked up the
teams' workflow while delivering excellent contributions.

For this past work, NoisyCoil sent mails using the email address noisycoil@tutanota.com
which is the one they're using on nm.debian.org, and they signed their work and
email using a GPG key with fingerprint 50CF C9D5 E5BD E1CB CA57  FD7B 6DF0 08E7 0F28 CBF7.

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 NoisyCoil as they
present themselves on nm.debian.org is the rightful owner of both email
noisycoil@tutanota.com and GPG key 50CF C9D5 E5BD E1CB CA57  FD7B 6DF0 08E7 0F28 CBF7.
Signed with key 1459 3BFF 4A5E BF6F E0E9 716E ECBE DBB6 07B9 B2BE 		View raw

Log

Date Author Action Content Public
2025-01-14 15:11 tiago req_approve Requirement approved yes

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: , , , ,