blob: 77106ed60458ea471c58a3de1ef5d6fad82d3673 (
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
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] slight security improvement: should we update aria2 to 1.11.2?
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20slight%20security%20improvement%3A%20should%20we%20update%0A%20aria2%20to%201.11.2%3F&In-Reply-To=%3Calpine.LMD.2.02.1105241228400.26021%40zem.cjw.nep%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="004930.html">
<LINK REL="Next" HREF="004935.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] slight security improvement: should we update aria2 to 1.11.2?</H1>
<B>Christiaan Welvaart</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20slight%20security%20improvement%3A%20should%20we%20update%0A%20aria2%20to%201.11.2%3F&In-Reply-To=%3Calpine.LMD.2.02.1105241228400.26021%40zem.cjw.nep%3E"
TITLE="[Mageia-dev] slight security improvement: should we update aria2 to 1.11.2?">cjw at daneel.dyndns.org
</A><BR>
<I>Tue May 24 12:30:27 CEST 2011</I>
<P><UL>
<LI>Previous message: <A HREF="004930.html">[Mageia-dev] slight security improvement: should we update aria2 to 1.11.2?
</A></li>
<LI>Next message: <A HREF="004935.html">[Mageia-dev] slight security improvement: should we update aria2 to 1.11.2?
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#4934">[ date ]</a>
<a href="thread.html#4934">[ thread ]</a>
<a href="subject.html#4934">[ subject ]</a>
<a href="author.html#4934">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>On Tue, 24 May 2011, Michael Scherer wrote:
><i> I would keep this as a update after the release is out ( like they 4
</I>><i> ruby cve, libzip one ( CVE-2011-0421 )) and others that came out since
</I>><i> yesterday.
</I>><i>
</I>><i> So maybe we could open bugs for this ?
</I>
><i> There is 2 proposal :
</I>><i> - filling them on security, and have a saved search
</I>
What do you mean by that, a security product?
><i> - creating a tracker bug
</I>><i>
</I>><i> I would be in favor of the tracker bug :
</I>><i> - you can subscribe to it
</I>><i> - it will be clearer ( as bugfixes are not security so we may miss some
</I>><i> update to do )
</I>><i> - it doesn't pollute the list of saved search
</I>><i>
</I>><i> But as pascal said, a tracker bug requires that each bug to be linked to
</I>><i> it, which is manual and error prone.
</I>
I don't know much about bugzilla, but:
- Add a keyword 'security' to all security bugs.
(also manual and error prone?)
- Set target to 'Mageia 1' for all bugs about stable updates.
Bugs about backports are not allowed to be targeted at a stable
release, we can add additonal backports targets if needed.
Having a saved search that can easily be found doesn't sound like a bad
idea. A tracker bug won't be closed even if all dependencies are resolved,
is that a good way to use tracker bugs?
Christiaan
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="004930.html">[Mageia-dev] slight security improvement: should we update aria2 to 1.11.2?
</A></li>
<LI>Next message: <A HREF="004935.html">[Mageia-dev] slight security improvement: should we update aria2 to 1.11.2?
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#4934">[ date ]</a>
<a href="thread.html#4934">[ thread ]</a>
<a href="subject.html#4934">[ subject ]</a>
<a href="author.html#4934">[ 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>
|
