1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-sysadm] [814] - add a module to generate gnupg key ( similar to the one for openssl
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-sysadm%40mageia.org?Subject=Re%3A%20%5BMageia-sysadm%5D%20%5B814%5D%20-%20add%20a%20module%20to%20generate%20gnupg%20key%0A%09%28%09similar%20to%20the%20one%20for%20openssl&In-Reply-To=%3C20110117170927.GH21938%40mars-attacks.org%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="002158.html">
<LINK REL="Next" HREF="002161.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-sysadm] [814] - add a module to generate gnupg key ( similar to the one for openssl</H1>
<B>nicolas vigier</B>
<A HREF="mailto:mageia-sysadm%40mageia.org?Subject=Re%3A%20%5BMageia-sysadm%5D%20%5B814%5D%20-%20add%20a%20module%20to%20generate%20gnupg%20key%0A%09%28%09similar%20to%20the%20one%20for%20openssl&In-Reply-To=%3C20110117170927.GH21938%40mars-attacks.org%3E"
TITLE="[Mageia-sysadm] [814] - add a module to generate gnupg key ( similar to the one for openssl">boklm at mars-attacks.org
</A><BR>
<I>Mon Jan 17 18:09:27 CET 2011</I>
<P><UL>
<LI>Previous message: <A HREF="002158.html">[Mageia-sysadm] [814] - add a module to generate gnupg key ( similar to the one for openssl
</A></li>
<LI>Next message: <A HREF="002161.html">[Mageia-sysadm] [814] - add a module to generate gnupg key ( similar to the one for openssl
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#2159">[ date ]</a>
<a href="thread.html#2159">[ thread ]</a>
<a href="subject.html#2159">[ subject ]</a>
<a href="author.html#2159">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>On Mon, 17 Jan 2011, Pascal Terjan wrote:
><i> > 1 key for all is the simplest solution, as this is easiest, and do not
</I>><i> > requires a lot of work to update keys. There is also a simpler BS.
</I>><i> > However, this mean we cannot expire the keys. But this also mean that we
</I>><i> > can more easily have it signed, if we make it signed once, and do not
</I>><i> > need to redo it every time. ( see the gpg web of trust ).
</I>><i>
</I>><i> Another solution is to have one key, signed by everyone and stored
</I>><i> safely (like, on a usb key in a bank), and use this key to sign the
</I>><i> keys that will sign packages (and that will be stored safely too but
</I>><i> have to be accessible on valstar). If we want to use a new key at some
</I>><i> point for signing packages, we just need to access that master key.
</I>
It looks like a good idea.
><i> >
</I>><i> > How do we sign
</I>><i> > ==============
</I>><i> >
</I>><i> > Again, point 3 have a impact here. Either we sign when uploaded, using
</I>><i> > youri, or using a custom action ( as current one do not permit to change
</I>><i> > uid ), or we use some custom cronjob to sign.
</I>
I vote too for using a custom action, to store the key on a separate
account, and use it with a script run with sudo.
It can be done with a cron job too, but it will slower I think. Is there
any advantage doing it with a cron job ?
><i> >
</I>><i> > Or we sign when the release is made.
</I>
That would mean having unsigned cauldron packages ?
><i> >
</I>><i> > I would recommend using a custom action, as privilege separation sound
</I>><i> > like a good idea. I would prefer to avoid signing again the day of
</I>><i> > release, for reasons that were already given.
</I>><i> >
</I>><i> >
</I>><i> > Bonus, usage of the module :
</I>><i> > ============================
</I>><i> >
</I>><i> >    gnupg::keys { "cauldron":
</I>><i> >        email => "root@$domain",
</I>><i> >        key_name => "John the plop",
</I>><i> >        key_length => "4096"
</I>><i> >    }
</I>><i> >
</I>><i> > create a key cauldron.sec and cauldron.pub in /etc/gnupg/keys/. I am not
</I>><i> > sure of the format ( maybe have it exported would be good ), and I am
</I>><i> > not sure that putting everything in this directory is the good location.
</I>
What are the permissions and owner on this directory ?
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="002158.html">[Mageia-sysadm] [814] - add a module to generate gnupg key ( similar to the one for openssl
</A></li>
<LI>Next message: <A HREF="002161.html">[Mageia-sysadm] [814] - add a module to generate gnupg key ( similar to the one for openssl
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#2159">[ date ]</a>
<a href="thread.html#2159">[ thread ]</a>
<a href="subject.html#2159">[ subject ]</a>
<a href="author.html#2159">[ author ]</a>
</LI>
</UL>
<hr>
<a href="https://www.mageia.org/mailman/listinfo/mageia-sysadm">More information about the Mageia-sysadm
mailing list</a><br>
</body></html>
|
