protonscr

should not need execmod access

steamopen Steam client
ValveSoftware/steam-for-linux#5340 · opened 2018-01-15 by etbe · updated 2019-07-18 · 0 comments · github
Eetbe 2018-01-15 github

Your system information

This is from version 1.0.0.54-3 of the Steam package on Debian, currently using Debian/Testing. I haven't selected the Steam beta program.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887348

I filed the above Debian bug report and was directed to report here as an upstream issue.

type=AVC msg=audit(1516012042.500:1381380): avc: denied { execmod } for pid=4488 comm="steam" path="/home/rjc/.steam/ubuntu12_32/libavutil.so.55" dev="sda2" ino=64950 scontext=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 context=unconfined_u:object_r:user_home_t:s0 tclass=file permissive=0

Above is an audit message from running steam with a fairly default SE Linux configuration in enforcing mode. The command "setsebool allow_execmod 1" permits this to work, but this should be fixed. Allowing execmod access weakens the security of the system in general, and when the shared object requests it the security of the application is weakened.

https://etbe.coker.com.au/2008/09/11/execmod-and-se-linux-i386-must-die/

Above is a blog post I wrote about this in 2008. The root cause of this is assembler optimisations for i386. If the steam package was released in an AMD64 variant then the default compile of libavutil would solve this problem (back in 2008 I spent a lot of time recompiling libabutil and related libraries to fix this on i386 while AMD64 just worked as desired).

https://etbe.coker.com.au/2007/02/10/execmod/

Here's another blog post I wrote about this. This is not just a SE Linux issue, this is an issue of generally weakening memory access permissions on Linux systems.

Nothing extracted yet.