Gentoo Archives: gentoo-commits

From: "Michał Górny" <mgorny@g.o>
To: gentoo-commits@l.g.o
Subject: [gentoo-commits] data/glep:master commit in: /
Date: Sun, 29 Jul 2018 20:51:10
Message-Id: 1532894846.e8a6c9fbdce6e47648f788ce310c21b96ed380d4.mgorny@gentoo
1 commit: e8a6c9fbdce6e47648f788ce310c21b96ed380d4
2 Author: Michał Górny <mgorny <AT> gentoo <DOT> org>
3 AuthorDate: Wed Jul 4 09:49:46 2018 +0000
4 Commit: Michał Górny <mgorny <AT> gentoo <DOT> org>
5 CommitDate: Sun Jul 29 20:07:26 2018 +0000
6 URL: https://gitweb.gentoo.org/data/glep.git/commit/?id=e8a6c9fb
7
8 glep-0063: Explain minimal & recommended sections
9
10 glep-0063.rst | 8 ++++++++
11 1 file changed, 8 insertions(+)
12
13 diff --git a/glep-0063.rst b/glep-0063.rst
14 index 14541d7..f4b49c2 100644
15 --- a/glep-0063.rst
16 +++ b/glep-0063.rst
17 @@ -41,6 +41,10 @@ Specifications for OpenPGP keys
18
19 Bare minimum requirements
20 -------------------------
21 +This section specifies obligatory requirements for all OpenPGP keys used
22 +to commit to Gentoo. Keys that do not conform to those requirements can
23 +not be used to commit.
24 +
25 1. SHA2-series output digest (SHA1 digests internally permitted),
26 256bit or more::
27
28 @@ -61,6 +65,10 @@ Bare minimum requirements
29
30 Recommendations
31 ---------------
32 +This section specifies the best practices for Gentoo developers.
33 +The developers should follow those practices unless there is a strong
34 +technical reason not to (e.g. hardware limitations, necessity of replacing
35 +their primary key).
36
37 1. Copy ``/usr/share/gnupg/gpg-conf.skel`` to ``~/.gnupg/gpg.conf``, append
38 the following block::