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