Key consistency checks

This requirement has been approved by ago.

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:

If the key does not meet these requirements, and you would struggle to create one which does, contact Front Desk.

This check will be approved manually by Front Desk as the application progresses.

Keycheck results

OpenPGP fingerprint D4EB 7D94 E78E 4EE8 ECE0 7F94 F879 6199 C045 86CE
Main key ok (last updated: 2020-01-26 18:14 UTC)
UID Richard Laager <rlaager, pidgin.im> ok, 0 non-DD sigs, 2 DD sigs:
  • 11192892EFD75934: Kenneth J. Pronovici <pronovic@ieee.org>
  • C9E55E2FADC8F4B9: Steve M. Robbins <steve@sumost.ca>
UID Richard Laager <rlaager, gmail.com> ok, 0 non-DD sigs, 2 DD sigs:
  • 11192892EFD75934: Kenneth J. Pronovici <pronovic@ieee.org>
  • C9E55E2FADC8F4B9: Steve M. Robbins <steve@sumost.ca>
UID Richard Laager <rlaager, wiktel.com> ok, 0 non-DD sigs, 2 DD sigs:
  • 11192892EFD75934: Kenneth J. Pronovici <pronovic@ieee.org>
  • C9E55E2FADC8F4B9: Steve M. Robbins <steve@sumost.ca>
UID Richard Laager <rlaager, coderich.net> ok, 0 non-DD sigs, 2 DD sigs:
  • 11192892EFD75934: Kenneth J. Pronovici <pronovic@ieee.org>
  • C9E55E2FADC8F4B9: Steve M. Robbins <steve@sumost.ca>

Log

Date Author Action Content Public
2020-01-27 14:37 mattia req_approve Requirement approved yes
2020-01-27 03:56 rlaager - IIRC, during my DM application, there was a comment about my 10 year key expiration. If that's a problem, I can set it to not expire or have a longer lifetime. yes
2020-01-27 03:55 rlaager - When I created this new key, I forgot that the latest self-signature is the "main" UID, so I ended up with rlaager@pidgin.im being the main UID. It doesn't really matter that much, but I can add a new self-signature to make something else the main UID (e.g. rlaager@wiktel.com to match my debian/control Maintainer: entries) if needed. yes