linux-kernel - [PATCH] pgpkeys: new keys need two signatures

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <20230716-fixes-v1-1-9802bf35ad6b@weissschuh.net>
Date:   Sun, 16 Jul 2023 21:38:19 +0200
From:   Thomas Weißschuh <linux@...ssschuh.net>
To:     Konstantin Ryabitsev <konstantin@...uxfoundation.org>
Cc:     linux-kernel@...r.kernel.org,
        Thomas Weißschuh <linux@...ssschuh.net>
Subject: [PATCH] pgpkeys: new keys need two signatures

Recent messages on the keys@...ux.kernel.org list indicate that two
signatures are needed.
This also matches the wording from accounts.rst.

Signed-off-by: Thomas Weißschuh <linux@...ssschuh.net>
---
 source/pgpkeys.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/source/pgpkeys.rst b/source/pgpkeys.rst
index 78ba703ff42b..ee2a912612f8 100644
--- a/source/pgpkeys.rst
+++ b/source/pgpkeys.rst
@@ -3,7 +3,7 @@ Kernel developer PGP keyring
 
 If you regularly contribute code to the Linux kernel, you are encouraged
 to submit your key to be included in the PGP keyring repository. For us
-to be able to accept it, it must have at least one signature from
+to be able to accept it, it must have at least two signatures from
 someone whose key is already in that repository, so we can trace each
 key's trust lineage to the head maintainer (Linus Torvalds).
 

---
base-commit: 8196a3c298d9b1f11be305c87eb890f44f7c8cc5
change-id: 20230716-fixes-b22a305dc9d2

Best regards,
-- 
Thomas Weißschuh <linux@...ssschuh.net>