Key consistency checks

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

This process has been closed by gwolf on 2021-02-04: 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	C450 1960 33B2 4682 EFE4 4C9D 7CB6 E83D 8605 423A
Main key	ok (last updated: 2025-01-13 02:36 UTC)
UID David Suárez Rodríguez (Actual) <david.sephirot, gmail.com>	ok, 1 non-DD sigs, 1 DD sigs: AEC828749D85C53C: James Bromberger (JEB) <james@rcpt.to>

Active key endorsements

Endorsed by

Date

Statement

Actions

jackyf

2020-12-01
(4 years, 1 month ago)

Although it looks like David has enough signatures from other sources now, I'm
adding it for posterity.


I have interacted with David using his present e-mail [1] and one of David's
previous keys [2], on numerous occasions in 2012, 2013 and 2014 by sponsoring
one of his packages. His application key [3] has a valid GPG signature from
key [2].

In 2019, we interacted briefly using key different from [2] and [3].

In 2020, I have interacted with David using his e-mail [1] and his DD
application key [3] by receiving signed e-mails from him. I have additionally
verified that, in 2020:
 - David can read an e-mail encrypted for him using key [2];
 - David can reproduce bits from our private communication in 2013 in a signed
   e-mail using key [3].

Therefore, I without a doubt conclude that David is in possession of e-mail
[1], keys [2][3], and is the same person I've interacted with starting back in
2012.


[1] david.sephirot@gmail.com
[2] 0x65C6949B0B33E24E
[3] 0x7CB6E83D8605423A

- --
Composed on 2020-12-01.

Signed with key 505D 0AA7 8F90 F6B2 3CC2 96A8 A7ED 831F 59B3 A0E8

View raw

Log

Date	Author	Action	Content	Public
2020-12-01 13:58	santiago	req_approve	Key signed by 2 DDs	yes
2020-11-07 14:20	peb	-	Alright! Feel free to have your endorsements submitted whenever you wish, but you'll have to wait for the official announcement of Endorsements being taken into account to have this keycheck approved.	yes
2020-11-07 14:18	deiv	-	Peb, I will go with new key endorsements way	yes
2020-11-07 13:54	peb	-	Hi, you'll need at least another key signature from a DD to proceed.	yes