| 1 |
On Tue, Mar 8, 2011 at 1:40 PM, Alex Efros wrote: |
| 2 |
> On Fri, Mar 06, 2009 at 03:25:16PM -0800, Ned Ludd wrote: |
| 3 |
>> > On Fri, Mar 06, 2009 at 11:12:59PM +0200, pageexec@××××××××.hu wrote: |
| 4 |
>> > > ah crap, i know what it is. it's a several years old glibc bug where someone |
| 5 |
>> > > put a certain variable into the RELRO segment but forgot that it'll be written |
| 6 |
>> > > to later when a library with RWE GNU_STACK is loaded. the workaround is |
| 7 |
>> > > to find that library (just extract them from strace, probably it'll be |
| 8 |
>> > > pari's library) and run execstack -c on it. |
| 9 |
>> > |
| 10 |
>> > I don't have execstack command. Looks like it belong to prelink package, |
| 11 |
>> > but http://www.gentoo.org/doc/en/prelink-howto.xml states it's |
| 12 |
>> > incompatible with hardened. Because of this I decide to compile it |
| 13 |
>> > manually, just to get execstack command: |
| 14 |
>> > |
| 15 |
>> > # emerge -f prelink |
| 16 |
>> > # cd /usr/src |
| 17 |
>> > # tar xjvf /usr/portage-distfiles/prelink-20071009.tar.bz2 |
| 18 |
>> > # cd prelink |
| 19 |
>> > # ./configure && make |
| 20 |
>> > |
| 21 |
>> > Now I tried your workaround: |
| 22 |
>> > |
| 23 |
>> > # /usr/src/prelink/src/execstack -c /usr/lib/perl5/site_perl/5.8.8/i686-linux/auto/Math/Pari/Pari.so |
| 24 |
>> > # /usr/src/prelink/src/execstack -c /usr/local/ioncube/ioncube_loader_lin_5.2.so |
| 25 |
>> > # /usr/src/prelink/src/execstack -c /usr/local/Zend/lib/ZendExtensionManager.so |
| 26 |
>> > # /usr/src/prelink/src/execstack -c /usr/local/Zend/lib/ZendExtensionManager_TS.so |
| 27 |
>> > # /usr/src/prelink/src/execstack -c /usr/local/Zend/lib/Optimizer-3.3.0/php-5.2.x/ZendOptimizer.so |
| 28 |
>> > |
| 29 |
>> > and it works!! |
| 30 |
>> > |
| 31 |
>> > Is this issue will be fixed in next stable hardened-sources? |
| 32 |
>> |
| 33 |
>> FYI.. PaX Team maintains the PaX kernel and has little control over what |
| 34 |
>> fixes go into the "next" hardened-sources. Also seems to me a little |
| 35 |
>> strange that the PaX Team would have to put a work-around in the kernel |
| 36 |
>> for a bug in glibc.. Seems like glibc should be fixed vs the kernel. |
| 37 |
> |
| 38 |
> 2 years later… Just updated system, bug still exists, and I still have to |
| 39 |
> use execstack workaround for zendoptimizer and ioncube. |
| 40 |
|
| 41 |
like they said, this doesnt seem to be a bug in the kernel, so the pax |
| 42 |
source arent going to be changing |
| 43 |
|
| 44 |
if there's a bug in glibc, an actual bug in bugs.g.o needs to be |
| 45 |
opened with real details/patches. otherwise, nothing is going to |
| 46 |
change. |
| 47 |
-mike |
Archives