Well ever since me, Mike and Alexandre did the preloader work a few years ago Wine itself has been execshield resistant, but the apps themselves may not be (my guess is that this is why Microsoft have not implemented it themselves ... that and they appear to be scared of their own dynamic linker code).
We could add the syscall to switch off execshield and get a legacy VMA layout to Wine itself, but Alexandre doesn't like it as the "ABI personality" syscall basically has no well defined behaviour at all and is used for all kinds of things, some of which may be useful. If there was an execshield/VMA randomization specific way to disable things on a per-process basis that'd be best. Otherwise I guess adding the personality syscall to the WoW patch wouldn't hurt, as it's already custom.
thanks -mike
On 5/2/06, n0dalus n0dalus+wine@gmail.com wrote:
On 5/1/06, Mike Hearn mike@plan99.net wrote:
Seems the WoW appdb page (apart from being a great example of what an appdb entry should be like!) recommends users patch their Wine to run WoW properly.
The patch mentioned particularly causes problems on systems like Fedora with randomized prelinking and exec-shield.
On FC5 it took me some time to get the patched version to run and used: setarch i386 -L wine WoW.exe -opengl
This apparently enables support for a legacy address layout. Does anyone know how this would allow it to run?
Just curious, n0dalus.