https://bugs.winehq.org/show_bug.cgi?id=36664
oiaohm oiaohm@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |oiaohm@gmail.com
--- Comment #6 from oiaohm oiaohm@gmail.com --- /proc/sys/abi/ldt16 I got version wrong its 3.15 where this offically will appear at kernel.org.
If you are on a 64 bit system that win16 does not work and its prior to 3.15 you might have /proc/sys/abi/ldt16 if you do enabling it will make it work again.
3.16 is when the hope for the secuirty patch will be done.
32 bit Linux kernels running 16 bit code is secure. The 64 bit mode requires a different fix to a secuity issue than.
Still does not change the fact that 3.15 after 16 bit support by kernel is optional on 64 bit systems. Someone without root rights will not be able to change /proc/sys/abi/ldt16 yet they will be able to change winecfg setting on prefix and end up in stuffed. LTS particular versions have had the disabling patch applied some have the /proc/sys/abi/ldt16 applied. As far as I can see no direct kernel.org kernel under 3.15 has the /proc/sys/abi/ldt16 patch applied yet.
From kernel.org 3.15+, 3.14.6+, 3.10.42 +, 3.4.92+ on has /proc/sys/abi/ldt16
in 64 bit mode but if you are running 3.12.21 or 3.2.59 those are busted. Hopefully 3.13.22 and 3.2.60 will have it but we will have to watch.
Just to bewarped 2.6.32.62 has not been patched at all.
Basically the faq will have to be updated a few times as the patches are pushed out. In the end there will be two lists.
List one will be kernels that contain /proc/sys/abi/ldt16 so 16 bit applications on these 64 bit kernels can be made work with secuirty risks. List two will be kernels that contain espfix64 these are safe to run 16 bit applications but you still have to turn 16 bit on as required. https://lkml.org/lkml/2014/5/4/346 espfix64 is qued for 3.16 and maybe backported to LTS kernels.
Why is espfix64 critical it contains the secuirty fix for 16 bit segments for 64 bit kernel.