wine vs. pax (failed to create the process heap)

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

wine vs. pax (failed to create the process heap)

Postby zyta2002 » Wed Mar 17, 2004 5:48 am

When I use pax (with a 2.6.3 kernel), I don't get wine to work.

The errormessage:


wine: failed to create the process heap
Wine failed with return code 1


I'v tried to disable all (possible) PAX features using chpax

Code: Select all
chpax -emrspx /usr/lib/wine/wine.bin


but this didn't helped :(

Do I have to disable PAX or do I have to remove some pax options from the Kernel ??

Code: Select all
workstation:/boot# grep PAX config-2.6.3
CONFIG_PAX=y
# CONFIG_PAX_SOFTMODE is not set
CONFIG_PAX_EI_PAX=y
CONFIG_PAX_PT_PAX_FLAGS=y
CONFIG_PAX_NO_ACL_FLAGS=y
# CONFIG_PAX_HAVE_ACL_FLAGS is not set
# CONFIG_PAX_HOOK_ACL_FLAGS is not set
CONFIG_PAX_NOEXEC=y
CONFIG_PAX_PAGEEXEC=y
CONFIG_PAX_SEGMEXEC=y
CONFIG_PAX_EMUTRAMP=y
CONFIG_PAX_MPROTECT=y
# CONFIG_PAX_NOELFRELOCS is not set
CONFIG_PAX_ASLR=y
CONFIG_PAX_RANDKSTACK=y
CONFIG_PAX_RANDUSTACK=y
CONFIG_PAX_RANDMMAP=y
CONFIG_PAX_RANDEXEC=y


Ingo Molnar added some code changes in his exec-shield patch. Is the problem on pax the same one ??


exec-shield-2.4.21-rc1-C5
turn off shlib relocation if the stack is executable. This is needed for Wine, qemu and other apps that need the low memory range.


Thanks in advice...
zyta2002
 
Posts: 2
Joined: Wed Mar 17, 2004 5:36 am

Re: wine vs. pax (failed to create the process heap)

Postby PaX Team » Wed Mar 17, 2004 8:08 pm

zyta2002 wrote:I'v tried to disable all (possible) PAX features using chpax

Code: Select all
chpax -emrspx /usr/lib/wine/wine.bin

for now you're best off by disabling PaX on all wine binaries.
Ingo Molnar added some code changes in his exec-shield patch. Is the problem on pax the same one ??

exec-shield-2.4.21-rc1-C5
turn off shlib relocation if the stack is executable. This is needed for Wine, qemu and other apps that need the low memory range.
PaX doesn't put stuff into the ascii-armor area (which overlaps the region expected by windows/PE executables) so there's no incompatibility in there. the reason that wine doesn't work with PaX is that some wine libraries contain code in their .data section which is non-executable, hopefully one day it'll be fixed.
PaX Team
 
Posts: 2310
Joined: Mon Mar 18, 2002 4:35 pm

Postby zyta2002 » Mon Mar 22, 2004 5:25 am

Great :D

Code: Select all
chpax -ermspx /usr/lib/wine/*


helped :wink:

Thanks !!
zyta2002
 
Posts: 2
Joined: Wed Mar 17, 2004 5:36 am


Return to grsecurity support