From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- zarb-ml/mageia-dev/20110131/002386.html | 85 +++++++++++++++++++++++++++++++++ 1 file changed, 85 insertions(+) create mode 100644 zarb-ml/mageia-dev/20110131/002386.html (limited to 'zarb-ml/mageia-dev/20110131/002386.html') diff --git a/zarb-ml/mageia-dev/20110131/002386.html b/zarb-ml/mageia-dev/20110131/002386.html new file mode 100644 index 000000000..8417bccf2 --- /dev/null +++ b/zarb-ml/mageia-dev/20110131/002386.html @@ -0,0 +1,85 @@ + + + + [Mageia-dev] PGP keys and package signing + + + + + + + + + +

[Mageia-dev] PGP keys and package signing

+ Christophe Fergeau + cfergeau at gmail.com +
+ Mon Jan 31 12:13:04 CET 2011 +

+
+ +
Hey,
+
+2011/1/31 nicolas vigier <boklm at mars-attacks.org>:
+>  - In case we think the packages@ key may have been compromised, or is
+>   too old, or we want to change it for any other reason, we revoke the
+>   key, and/or revoke the signature from board@ so that it is no
+>   longer accepted by urpmi. We create a new key, we sign it with
+>   the board@ key and we can start to use this new key.
+
+Will all existing packages be reviewed and resigned when they key is
+thought to have been compromised? What happens on user systems when
+this is done? Will they have to reinstall all packages signed with the
+new key?
+
+Christophe
+
+ + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ -- cgit v1.2.1