summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/20110516/004709.html
blob: d9565d2467519cb453f043d15c1911850141a7bb (plain)
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
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
 <HEAD>
   <TITLE> [Mageia-dev] Security Update Process
   </TITLE>
   <LINK REL="Index" HREF="index.html" >
   <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Security%20Update%20Process&In-Reply-To=%3CBANLkTi%3DEb9jpWNedVFLuO5LEJ01fpiOmcQ%40mail.gmail.com%3E">
   <META NAME="robots" CONTENT="index,nofollow">
   <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
   <LINK REL="Previous"  HREF="004708.html">
   <LINK REL="Next"  HREF="004713.html">
 </HEAD>
 <BODY BGCOLOR="#ffffff">
   <H1>[Mageia-dev] Security Update Process</H1>
    <B>Pascal Terjan</B> 
    <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Security%20Update%20Process&In-Reply-To=%3CBANLkTi%3DEb9jpWNedVFLuO5LEJ01fpiOmcQ%40mail.gmail.com%3E"
       TITLE="[Mageia-dev] Security Update Process">pterjan at gmail.com
       </A><BR>
    <I>Mon May 16 16:57:25 CEST 2011</I>
    <P><UL>
        <LI>Previous message: <A HREF="004708.html">[Mageia-dev] Security Update Process
</A></li>
        <LI>Next message: <A HREF="004713.html">[Mageia-dev] Security Update Process
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#4709">[ date ]</a>
              <a href="thread.html#4709">[ thread ]</a>
              <a href="subject.html#4709">[ subject ]</a>
              <a href="author.html#4709">[ author ]</a>
         </LI>
       </UL>
    <HR>  
<!--beginarticle-->
<PRE>On Mon, May 16, 2011 at 15:45, Stew Benedict &lt;<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">stewbintn at gmail.com</A>&gt; wrote:
&gt;<i> OK,
</I>&gt;<i>
</I>&gt;<i> Mageia 1 is approaching quickly and we need to get our process in place
</I>&gt;<i> for security updates. We talked a bit about it a few weeks ago, and I
</I>&gt;<i> started a wiki page, but it needs more detail. Anne and I chatted on IRC
</I>&gt;<i> and it looks like we'll want to cutoff the &quot;on the iso &quot; updates at the
</I>&gt;<i> end of this week, so we need a process in place to release post-iso updates.
</I>&gt;<i>
</I>&gt;<i> ref: <A HREF="http://mageia.org/wiki/doku.php?id=security">http://mageia.org/wiki/doku.php?id=security</A>
</I>&gt;<i>
</I>&gt;<i> As I see it, initially we need, in no particular order:
</I>&gt;<i>
</I>&gt;<i> 1) a means to build updates for the release (iurt setup for mga1?)
</I>
A iurt setup for mga1 will exist anyway, what is missing is a way to
later upload to non public place.
Initially, we can just setup youri to restrict submitting a build to
updates_testing or updates to the secteam and it should be enough.

&gt;<i> 2) a means to publish updates (mail list, web page)
</I>&gt;<i> 3) a means to manage/track the updates (bugzilla?)
</I>&gt;<i> 4) work out/publish the process so we all know how it works
</I>&gt;<i>
</I>&gt;<i> And then of course we need people to be aware of vulnerabilities as they
</I>&gt;<i> are exposed. For now, we'll have be be slightly trailing until we can
</I>&gt;<i> show a history of releasing updates and hopefully gain access to the
</I>&gt;<i> closed list to get access to embargoed issues. Once that happens we will
</I>&gt;<i> possibly need additional infrastructure changes to keep the work
</I>&gt;<i> non-public before the embargo date.
</I>&gt;<i>
</I>&gt;<i> osvdb has a nice email aggregator that sends all the distro update
</I>&gt;<i> announcements, and the oss-security list has many of the CVE requests.
</I>&gt;<i> Unfortunately, my personal time hasn't allowed much more than a quick
</I>&gt;<i> read as they go by :/ I know many of you have been doing security
</I>&gt;<i> related bug reports and updates, which is great, thank-you. If anyone
</I>&gt;<i> wants to take a larger role in managing the process I'm more than happy
</I>&gt;<i> to let that happen. While I have experience, the time I'm able to commit
</I>&gt;<i> is less than helpful.
</I>&gt;<i>
</I>&gt;<i> Comments, volunteers?
</I></PRE>






<!--endarticle-->
    <HR>
    <P><UL>
        <!--threads-->
	<LI>Previous message: <A HREF="004708.html">[Mageia-dev] Security Update Process
</A></li>
	<LI>Next message: <A HREF="004713.html">[Mageia-dev] Security Update Process
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#4709">[ date ]</a>
              <a href="thread.html#4709">[ thread ]</a>
              <a href="subject.html#4709">[ subject ]</a>
              <a href="author.html#4709">[ author ]</a>
         </LI>
       </UL>

<hr>
<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev
mailing list</a><br>
</body></html>