GLEP 63: Gentoo OpenPGP policies
|Author||Robin H. Johnson <firstname.lastname@example.org>, Andreas K. Hüttel <email@example.com>, Marissa Fischer <firstname.lastname@example.org>, Michał Górny <email@example.com>|
|Posting history||2013-11-10, 2018-07-03, 2018-07-21|
Many developers and external sources helped in this GLEP.
This GLEP provides both a minimum requirement and a recommended set of OpenPGP key management policies for the Gentoo Linux distribution.
The distinct minimal and recommended expirations have been replaced by a single requirement. The rules have been simplified to use the same maximum time of 900 days for both the primary key and subkeys.
An additional rule requesting key renewal 2 weeks before expiration has been added. This is in order to give services and other developers time to refresh the key.
The usage of DSA keys has been disallowed.
The gpgfingerprint LDAP field has been altered to remove optional whitespace.
The gpg.conf contents have been removed as they were seriously outdated and decreased security over the modern defaults.
The requirement of SHA-2 digest has been extended to apply to self- signatures made on subkeys.
An additional requirement for @gentoo.org UID has been added.
The recommended RSA key size has been changed from 4096 bits to 2048 bits to match the GnuPG recommendations . The larger recommendation was unjustified and resulted in people unnecessarily replacing their RSA-2048 keys.
Minimal specification has been amended to allow for ECC keys.
The option of using DSA subkey has been removed from recommendations. The section now specifies a single recommendation of using RSA.
Given the increasing use and importance of cryptographic protocols in internet transactions of any kind, unified requirements for OpenPGP keys used in Gentoo Linux development are sorely needed. This document provides both a set of bare minimum requirements and a set of best practice recommendations for the use of GnuPG (or other OpenPGP providers) by Gentoo Linux developers. It is intended to provide a basis for future improvements such as, e.g., consistent ebuild or package signing and verifying by end users.
This section specifies obligatory requirements for all OpenPGP keys used to commit to Gentoo. Keys that do not conform to those requirements can not be used to commit.
- SHA-2 series output digest (SHA-1 digests internally permitted), at least 256-bit. All subkey self-signatures must use this digest.
- Signing subkey that is different from the primary key, and does not have any other capabilities enabled.
- Primary key and the signing subkey are both of type EITHER:
- RSA, >=2048 bits (OpenPGP v4 key format or later only),
- ECC curve 25519.
- Expiration date on key and all subkeys set to no more than 900 days into the future.
- Key expiration date renewed at least 2 weeks before the previous expiration date.
- UID using your @gentoo.org e-mail included in the key.
- Upload your key to the SKS keyserver rotation before usage!
This section specifies the best practices for Gentoo developers. The developers should follow those practices unless there is a strong technical reason not to (e.g. hardware limitations, necessity of replacing their primary key).
- Primary key and the signing subkey are both of type RSA, 2048 bits (OpenPGP v4 key format or later).
- Key expiration renewed annually to a fixed day of the year.
- Create a revocation certificate & store it hardcopy offsite securely (it's about ~300 bytes).
- Encrypted backup of your secret keys.
All Gentoo developers must list the complete fingerprint for their primary keys in the "gpgfingerprint" LDAP field. It must be exactly 40 hex digits, uppercase, without whitespace.
The prior "gpgkey" field will be removed, as it is a subset of the fingerprint field. In any place that presently displays the "gpgkey" field, the last 16 hex digits of the fingerprint should be displayed instead.
There is no consistent standard for GPG usage in Gentoo to date. There is conflicting information in the Devmanual  and the GnuPG Gentoo user guide . As there is little enforcement of Manifest signing and very little commit signing to date, there are no backwards compatibility concerns.
Much of the above was driven by the following:
|||GnuPG FAQ: Why doesn’t GnuPG default to using RSA-4096? (https://www.gnupg.org/faq/gnupg-faq.html#no_default_of_rsa4096)|
|||Debian GPG documentation (https://wiki.debian.org/Keysigning)|
|||Ana's blog: Creating a new GPG key (http://ekaia.org/blog/2009/05/10/creating-new-gpgkey/)|
|||RiseUp.net OpenPGP best practices (https://help.riseup.net/en/security/message-security/openpgp/best-practices)|
|||Gentoo Development Guide: Manifest (http://devmanual.gentoo.org/general-concepts/manifest/index.html)|
|||GnuPG Gentoo User Guide (http://www.gentoo.org/doc/en/gnupg-user.xml)|
|||NIST SP 800-57: Recommendation for Key Management: Part 1: General (Revision 3) (http://csrc.nist.gov/publications/nistpubs/800-57/sp800-57_part1_rev3_general.pdf)|
|||NIST SP 800-57: Recommendation for Key Management: Part 2: Best Practices for Key Management Organization (http://csrc.nist.gov/publications/nistpubs/800-57/SP800-57-Part2.pdf)|
|||Including the entire fingerprint of the issuer in an OpenPGP certification (http://thread.gmane.org/gmane.mail.notmuch.general/3721/focus=7234)|
|||ENISA Algorithms, Key Sizes and Parameters Report, 2013 recommendations, version 1.0 (October 2013) (https://www.enisa.europa.eu/activities/identity-and-trust/library/deliverables/algorithms-key-sizes-and-parameters-report)|