• People
  • Site wizard
  • Wiki help
  • kaliko
    DDPO Portfolio Contributor
  • Login
  1. Geoffroy Youri Berret
  2. Debian Maintainer
  3. 285: Key consistency checks

Key consistency checks

This requirement has been approved by Santiago Ruano Rincón <santiagorr@riseup.net> 7 years, 1 month ago.

This process has been closed by gwolf on 2018-04-11: no further modifications are possible.

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 2255 310A D1A2 48A0 7B59 7638 065F E539 32DC 551D
Main key ok (last updated: 2025-05-07 03:47 UTC)
UID Geoffroy Youri Berret <efrim, azylum.org> ok, 1 non-DD sigs, 1 DD sigs:
  • 96BD4FF64E709FDE: Alban Vidal <alban.vidal@zordhak.fr>
UID Jack Kaliko (dev id) <kaliko, azylum.org> ok, 0 non-DD sigs, 1 DD sigs:
  • 96BD4FF64E709FDE: Alban Vidal <alban.vidal@zordhak.fr>
UID Geoffroy Berret <geoffroy.berret, azylum.org> ok, 1 non-DD sigs, 1 DD sigs:
  • 96BD4FF64E709FDE: Alban Vidal <alban.vidal@zordhak.fr>
UID Geoffroy Youri Berret <kaliko, debian.org> ok, 0 non-DD sigs, 0 DD sigs:
  • none

Active key endorsements

Endorsed by Date Statement Actions
fsfs 2021-11-09
(3 years, 6 months ago)
For nm.debian.org, at 2021-11-09:

For the past several years (roughly: since late 2018), I have worked with
Geoffroy Youri Berret (kaliko) on the mpd-team, packaging MPD as well as some
of its clients (ncmpc, libmpdclient).

For this past work, Geoffroy Youri Berret sent mails using the email address
kaliko@azylum.org and sometimes efrim@azylum.org, and they consistently signed
their email using a GPG key with fingerprint 2255 310A D1A2 48A0 7B59  7638
065F E539 32DC 551D.

Due to the long-term interactions we had, I'm convinced that Geoffroy Youri
Berret as they present themselves on nm.debian.org is the rightful owner of
both email kaliko@azylum.org/efrim@azylum.org and GPG key 2255 310A D1A2 48A0
7B59  7638 065F E539 32DC 551D.
Signed with key 30B2 3C8B 4E6A 3B09 EAA6 B652 1297 3B6E 72DC 07B5
View raw

Log

Date Author Action Content Public
2018-03-26 13:12 santiago req_approve Requirement approved yes
2018-03-25 09:18 kaliko - Add DD signature yes
2017-09-06 12:40 kaliko - Hi Jonathan, The "kaliko" id is actually my dev pseudo. Concerning DD signatures, I'm waiting for an IRL meeting to exchange fingerprint/keys. yes
2017-09-05 22:42 jmw - I need to understand why there are two very different UIDs on this key, plus it needs a DD signature. 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: , , , ,