Gentoo Archives: gentoo-hardened

From: "Tóth Attila" <atoth@××××××××××.hu>
To: gentoo-hardened@l.g.o
Subject: Re: [gentoo-hardened] relocation error because of missing __guard since upgrading to glibc-2.13
Date: Thu, 10 Feb 2011 16:52:35
Message-Id: e825b14c329c99a4c1f80914afe38ada.squirrel@atoth.sote.hu
In Reply to: Re: [gentoo-hardened] relocation error because of missing __guard since upgrading to glibc-2.13 by "Anthony G. Basile"
1 Dear Blueness,
2
3 Thanks for your response.
4 There were quite some outdated ebuilds and abandoned dependencies amongst
5 the involved packages.
6 However there were some mentionable, like vixie-cron or portmap.
7 Fortunately my gcc-config is correct. The symptoms popped up probably
8 because I don't recompile system or world. I let the system roll and rely
9 on revdep-rebuild for consistency.
10
11 Probably the latest glibc stopped exporting some obsolete symbols.
12 Actually I'm happy, that it pointed on some elderly packages of my systems
13 older than 5 years now. Constantly hardened!
14
15 Regards:
16 Dw.
17
18 Attila is my firstname. Hungary is big-endian regarding name ordering...
19 :) Or simply call me Dwokfur.
20 --
21 dr Tóth Attila, Radiológus, 06-20-825-8057
22 Attila Toth MD, Radiologist, +36-20-825-8057
23
24 2011.Február 10.(Cs) 16:27 időpontban Anthony G. Basile ezt írta:
25 > Hi Toth,
26 >
27 > You're getting that error because you have something compiled with
28 > gcc-3. Make sure you're using gcc-4.4.4-r2 with the hardened specs. If
29 > you do gcc-config -l, you should see something like this:
30 >
31 > blueness@whiteness ~ $ gcc-config -l
32 > [1] x86_64-pc-linux-gnu-4.4.4 *
33 > [2] x86_64-pc-linux-gnu-4.4.4-hardenednopie
34 > [3] x86_64-pc-linux-gnu-4.4.4-hardenednopiessp
35 > [4] x86_64-pc-linux-gnu-4.4.4-hardenednossp
36 > [5] x86_64-pc-linux-gnu-4.4.4-vanilla
37 >
38 > We're not supporting hardening on gcc-3 anymore.
39 >
40 > On 02/10/2011 07:17 AM, "Tóth Attila" wrote:
41 >> Some binaries are failing since the last glibc upgrade like this:
42 >> -
43 >> binaryname: relocation error: binaryname: symbol __guard, version
44 >> GLIBC_2.3.2 not defined in file libc.so.6 with link time reference
45 >> -
46 >> I'm actually surprised how well my machines doing despite this problem.
47 >>
48 >> For those who have the same problem, you can search for affected
49 >> binaries
50 >> using this command:
51 >> -
52 >> scanelf -qRs __guard /bin /lib /sbin /usr/bin /usr/lib /usr/sbin /opt
53 >> /var/www/
54 >> -
55 >>
56 >> -
57 >> equery belongs path/binary
58 >> -
59 >> command can be used to query for which package the binary belongs to.
60 >>
61 >> Can somebody update me on the nature of the problem? Is it an intended
62 >> movement to drop __guard? I know, that it's obsolete. I would suggest to
63 >> communicate this in an enews or whatever for all hardened users. Or I
64 >> may
65 >> be the only one, who rolls the system without regular world recompiles?
66 >>
67 >> Regards:
68 >> Dwokfur
69 >
70 >
71 > --
72 > Anthony G. Basile, Ph.D.
73 > Gentoo Developer
74 >
75 >