• People
  • Site wizard
  • Wiki help
  • gioele
    DDPO Portfolio Contributor
  • Login
  1. Gioele Barabucci
  2. Debian Developer, uploading
  3. 1329: Key consistency checks

Key consistency checks

This requirement has been approved by Tiago Bortoletto Vaz <tiago@debian.org> 8 months, 3 weeks ago.

This process has been closed by johns on 2024-12-15: no further modifications are possible.

Potential problems

  • 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 0298 8A8F 528F A493 E1B9 8E38 8F89 871C DB75 972E
Main key key_encryption_expires_soon key_signing_expires_soon (last updated: 2025-05-24 01:06 UTC)
UID Gioele Barabucci <gioele, svario.it> ok, 0 non-DD sigs, 3 DD sigs:
  • 9C31503C6D866396: Stefano Zacchiroli <zack@upsilon.cc>
  • D5085A0750FDB7A3: Emanuele Rocca <ema@debian.org>
  • E6FFF1E38DC968B0: Marco d'Itri <md@linux.it>

Active key endorsements

Endorsed by Date Statement Actions
bluca 2022-11-06
(2 years, 6 months ago)
For nm.debian.org, at 2022-11-06:
For the past year or so, I have worked with Gioele Barabucci on systemd, debhelper and more.

For this past work, Gioele Barabucci sent mails using the email address gioele@svario.it
which is the one they're using on nm.debian.org, and they signed their work and
email using a GPG key with fingerprint 0298 8A8F 528F A493 E1B9  8E38 8F89 871C DB75 972E.

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 Gioele Barabucci as they
present themselves on nm.debian.org is the rightful owner of both email
gioele@svario.it and GPG key 0298 8A8F 528F A493 E1B9  8E38 8F89 871C DB75 972E.
EOF
Signed with key A9EA 9081 724F FAE0 484C 35A1 A81C EA22 BC8C 7E2E
View raw

Log

Date Author Action Content Public
2024-09-08 18:30 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: , , , ,