1 |
Nagy Gabor Peter wrote: |
2 |
> Hi list, |
3 |
> |
4 |
> I have a question: |
5 |
> |
6 |
> Since I am new to gentoo, I don't know how security updates work. |
7 |
> |
8 |
> I know Debian. In Debian if I have stable installed on a production |
9 |
> server, I get regular security fixes, often backported from the current |
10 |
> bleeding edge version, where upstream has fixed the bug to the version |
11 |
> that Debian stable contains. |
12 |
> |
13 |
> I have noticed that in gentoo there are many versions of a package that |
14 |
> are considered stable. Take glibc as an example, according to |
15 |
> http://packages.gentoo.org/search/?sstring=glibc, on x86 there are 8 |
16 |
> versions available, all of them stable. |
17 |
> |
18 |
> I have now two gentoo machines, one is going to be production, the |
19 |
> other is used to get me a little bit more familiar with the system. |
20 |
> |
21 |
> On the playground machine I have 2006.1 installed, glibc 2.4-r3 |
22 |
> On the production machine I have 2006.0, switched to hardened profile, |
23 |
> and then recompile, there I have glibc 2.3.6-r5 |
24 |
> |
25 |
> I see now that glibc 2.4-r3 should be upgraded to 2.4-r4 (by the way, |
26 |
> where can I check the differences (Changelog) between two gentoo |
27 |
> versions (like r3 and r4)?) |
28 |
|
29 |
On the packages.gentoo.org there is a link to the changelog that |
30 |
describes major changes to ebuilds. |
31 |
|
32 |
> |
33 |
> So my question: If someone finds a bug in glibc that gets corrected, |
34 |
> what does the gentoo maintainers do about it? Do they backport the fix |
35 |
> in all 8 versions? Or just in some of the versions and mark the not |
36 |
> fixed ones ~? |
37 |
|
38 |
Mostly, when a package (f.i. glibc-2.3.6-r5) contains a bug, a new |
39 |
ebuild is released under a new revision (in this example: |
40 |
glibc-2.3.6-r6) and then marked stable. The vulnerable ebuild will be |
41 |
removed. Users do an 'emerge --sync && emerge -uD world' and get the new |
42 |
glibc installed. |
43 |
|
44 |
|
45 |
> |
46 |
> Is there some mailinglist (like debian-security-announce) where such |
47 |
> security fixes are announced? |
48 |
|
49 |
Security are announced on the gentoo-announce mailing list, see |
50 |
http://www.gentoo.org/main/en/lists.xml for more info. |
51 |
|
52 |
> |
53 |
> What is the reason that the hardened profile selects the 2.3.6 version |
54 |
> instead of the 2.4? I mean not in glibc's case only, but generally. |
55 |
> |
56 |
> Does libc 2.4 have troubles with ssp? |
57 |
> |
58 |
|
59 |
Support for PIE and/or SSP is not complete for glibc >2.3 and gcc 4. |
60 |
There was some overlay with usable ebuilds for these versions |
61 |
|
62 |
I'm not sure about the reason why it doesn't work yet and why it takes |
63 |
so much trouble, there are some ppl on this list who can explain that |
64 |
far better... |
65 |
|
66 |
|
67 |
Tom |