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
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] Meeting for secteam start
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Meeting%20for%20secteam%20start&In-Reply-To=%3C4DA83B9C.6090207%40gmail.com%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="003997.html">
<LINK REL="Next" HREF="004003.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] Meeting for secteam start</H1>
<B>Stew Benedict</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Meeting%20for%20secteam%20start&In-Reply-To=%3C4DA83B9C.6090207%40gmail.com%3E"
TITLE="[Mageia-dev] Meeting for secteam start">stewbintn at gmail.com
</A><BR>
<I>Fri Apr 15 14:35:40 CEST 2011</I>
<P><UL>
<LI>Previous message: <A HREF="003997.html">[Mageia-dev] [895] - use File::Path and List::MoreUtils, and only import if_ from MDK:: Common
</A></li>
<LI>Next message: <A HREF="004003.html">[Mageia-dev] Meeting for secteam start
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#3999">[ date ]</a>
<a href="thread.html#3999">[ thread ]</a>
<a href="subject.html#3999">[ subject ]</a>
<a href="author.html#3999">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Sorry if I break the thread, just signed back up to the list.
Just to kick things off for secteam, I thought I'd list the process as I
remember it from when I worked with Vincent for a couple of years.
Not to say Mageia needs to follow any of this, and as we're a volunteer
organization, I suspect things will be structured a bit differently from
a staffing POV than "2 guys mostly dedicated to updates"
Old Process:
* monitor vendor-sec, discuss vulns, patches, negotiate release schedule,
also watch other distro updates, for things we may have missed
* check our srpm database (Vincent later reworked this) for all the
places the affected source code
may be buried (many packages embed copies of other source)
* apply/adapt patches for all supported releases/architectures (may have
been published on vendor-sec,
or from another distro package, or extracted from upstream)
** when we we supporting several releases, with Enterprise stuff
being quite old, reworking the patches at times was difficult
** policy changed over time and these days many things bump up to a
new release, rather than patching
* build in chroot to preserve the original build env (moved to iurt
around the time I left)
** if we had trouble building the package, contact the maintainer for
help
* acquire or write a POC (proof of concept) to test that the vuln is
corrected, if not, re-patch/re-test
* test the app for basic functionality, that we haven't introduced
regressions
** bugfix updates went to QA for testing, this was a big
blocker/delay at times
* write advisory text (usually copied from the CVE if there is one, or
bugzilla from a bugfix)
* upload packages to main mirror, wait a few hours and release the
announcement (we had several scripts
that facilitated getting packages in the right place, signing them,
uploading, etc.)
--
Stew Benedict
New Tazewell, TN
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="003997.html">[Mageia-dev] [895] - use File::Path and List::MoreUtils, and only import if_ from MDK:: Common
</A></li>
<LI>Next message: <A HREF="004003.html">[Mageia-dev] Meeting for secteam start
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#3999">[ date ]</a>
<a href="thread.html#3999">[ thread ]</a>
<a href="subject.html#3999">[ subject ]</a>
<a href="author.html#3999">[ 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>
|
