-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Should allow running programs from /usr/lib and /usr/libexec #227
Comments
Allows files in `/usr/libexec` and `/usr/lib` to execute. See canonical/steam-snap#227 for context.
@alexmurray what are your thoughts on allowing ixr for /usr in the steam-support interface as a means to future proof the steam snap? |
@kenvandine I don't see any good reason to not allow such a change - AFAIU this content is all controlled via steam and it could just as easily put something into |
canonical/snapd#12823 was merged and should be live in snapd edge. |
Allows files in `/usr/libexec` and `/usr/lib` to execute. See canonical/steam-snap#227 for context.
Describe the bug
Please see ValveSoftware/steam-runtime#586, which is a broader issue in which a user reports that Dota 2 (in a Steam Linux Runtime container) doesn't work in the Snap-packaged version of Steam.
The part I'm referring to in this particular issue report is:
To Reproduce
I've been unable to start Steam as a Snap app successfully myself, but presumably something like this:
Install and run Steam as a Snap app. Retrieve Steam -> Help -> System Information.
Expected behavior
Diagnostic programs in the Steam Linux Runtime container's /usr/libexec/ should be runnable. We don't currently install diagnostic programs into /usr/lib, but we might in future, and if we do, those should be runnable too.
In fact https://github.com/snapcore/snapd/blob/master/interfaces/builtin/steam_support.go appears to allow running anything matching
/usr/bin/**
or/usr/sbin/**
, but not/usr/libexec/**
or/usr/lib/**
.Granting
ixr
access to all of/usr
would be a lot more future-proof: we cannot predict what pressure-vessel will need to do to accommodate future OSs, app frameworks and games. There is no security benefit in preventing access to any of this - the same files can be accessed via $HOME anyway - so the only thing that's being achieved by having such a fine-grained AppArmor profile is to stop future versions of Steam from working reliably.The text was updated successfully, but these errors were encountered: