slackware 10.1: glibc 2.3.4 and grsecurity for 2.4.29

Discuss usability issues, general maintenance, and general support issues for a grsecurity-enabled system.

slackware 10.1: glibc 2.3.4 and grsecurity for 2.4.29

Postby InHeLL » Tue Feb 08, 2005 5:19 pm

I recompilled the vanilla kernel from kernel.org and added the grsec patch and after that..nothing worked:

root@hera/etc/rc.d# nmap
nmap: error while loading shared libraries: libcrypto.so.0: cannot enable
executable stack as shared object requires: Permission denied

root@hera/etc/rc.d# pico
pico: error while loading shared libraries: libncurses.so.5: cannot enable
executable stack as shared object requires: Permission denied

root@hera/etc/rc.d# /etc/rc.d/rc.httpd start
Syntax error on line 6 of /etc/apache/mod_php.conf:
Cannot load /usr/libexec/apache/libphp4.so into server: libcrypto.so.0:
cannot enable executable stack as shared object requires: Permission denied
/usr/sbin/apachectl start: httpd could not be started

root@hera/etc/rc.d# host
host: error while loading shared libraries: libcrypto.so.0: cannot enable
executable stack as shared object requires: Permission denied


after that I recompiled the vanilla kernel without grsec and everything worked fine.

I also recompiled 2.4.29 kernel with grsec on a snapshot of slackware-current before glibc 2.3.4 was merged into slack, and worked fine there too.
InHeLL
 
Posts: 3
Joined: Fri Apr 16, 2004 1:45 am

Re: slackware 10.1: glibc 2.3.4 and grsecurity for 2.4.29

Postby PaX Team » Tue Feb 08, 2005 5:51 pm

InHeLL wrote:nmap: error while loading shared libraries: libcrypto.so.0: cannot enable
executable stack as shared object requires: Permission denied
search the forums for that error message, it's been explained many times now.
PaX Team
 
Posts: 2310
Joined: Mon Mar 18, 2002 4:35 pm


Return to grsecurity support