search for: wine_exec_t

...to /usr/bin/wine/* (e.g. the main executable is /usr/bin/wine/wine) (so that when I want to wipe all the wine binaries for a new clean install I can do so easily) I relabled the security context of all the /usr/bin/wine/* and /usr/lib/wine/*so files (e.g. -rwxr-xr-x root root system_u:object_r:wine_exec_t /usr/bin/wine/wine -rwxr-xr-x root root system_u:object_r:textrel_shlib_t /usr/lib/wine/activeds.dll.so ) but I still get a "wine_main_preload_info not found" from wine when it starts. The Wine source leads me to believe this is because Wine is not able to load the wine-preloader. I&...

...context=user_u:system_r:unconfined_t:s0 tcontext=user_u:system_r:unconfined_t:s0 tclass=process * If I set the security contect for the binary "casio" the same as "wine" then it runs: >[wowbaggr@surfer bin]$ ls -lZ casio >-rwxr-xr-x wowbaggr wowbaggr system_u:object_r:wine_exec_t casio This leads me to the conclusion that ideally, when run as the interpreter for a PE executable via binfmt_misc, Wine needs to set the process security context appropriately to allow for programs to run. I've not looked into whether it is possible for a running process to change its...