[GH-ISSUE #5257] steam: profile creates a bunch of directories #2937

Closed
opened 2026-05-05 09:35:57 -06:00 by gitea-mirror · 3 comments
Owner

Originally created by @m00nwtchr on GitHub (Jul 19, 2022).
Original GitHub issue: https://github.com/netblue30/firejail/issues/5257

...Why?

I can't even get rid of it properly because of Error: maximum 32 --ignore options are permitted

Originally created by @m00nwtchr on GitHub (Jul 19, 2022). Original GitHub issue: https://github.com/netblue30/firejail/issues/5257 ...Why? I can't even get rid of it properly because of `Error: maximum 32 --ignore options are permitted`
Author
Owner

@rusty-snake commented on GitHub (Jul 19, 2022):

For questions we have Discussions (this is an issue tracker) and for bugs we have a template.

...Why?

Because steam.profile is a whitelisting profile and you can only whitelist existing files.

I can't even get rid of it properly because of Error: maximum 32 --ignore options are permitted

ignore mkdir

<!-- gh-comment-id:1189021028 --> @rusty-snake commented on GitHub (Jul 19, 2022): For questions we have Discussions (this is an issue tracker) and for bugs we have a template. > ...Why? Because steam.profile is a whitelisting profile and you can only whitelist existing files. > I can't even get rid of it properly because of `Error: maximum 32 --ignore options are permitted` `ignore mkdir`
Author
Owner

@m00nwtchr commented on GitHub (Jul 19, 2022):

  1. Why can you only whitelist existing files?
  2. Still, they shouldn't be in the profile by default, rather something the user can add to their steam.local if they use that game/application. (in case someone e.g. doesn't check the profile file first, and launches steam after a firecfg and now has to get rid of all this crap)
<!-- gh-comment-id:1189022209 --> @m00nwtchr commented on GitHub (Jul 19, 2022): 1. Why can you only whitelist existing files? 2. Still, they shouldn't be in the profile by default, rather something the user can add to their `steam.local` if they use that game/application. (in case someone e.g. doesn't check the profile file first, and launches steam after a `firecfg` and now has to get rid of all this crap)
Author
Owner

@rusty-snake commented on GitHub (Jul 19, 2022):

  1. Technical reasons. Whitelisting is implemented with bind-mounts.
  2. There are two kinds of users, technical users who notice this hidden files and nontechnical users who do bit notice those hidden files (and don't know that hidden files exist on a computer). The first category can edit configuration files, the later don't and would only notice that game states are not saved and stop using a sandbox. The default configuration should cover the most use cases and should work for nontechnical users by default.
<!-- gh-comment-id:1189029169 --> @rusty-snake commented on GitHub (Jul 19, 2022): 1. Technical reasons. Whitelisting is implemented with bind-mounts. 2. There are two kinds of users, technical users who notice this hidden files and nontechnical users who do bit notice those hidden files (and don't know that hidden files exist on a computer). The first category can edit configuration files, the later don't and would only notice that game states are not saved and stop using a sandbox. The default configuration should cover the most use cases and should work for nontechnical users by default.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/firejail#2937
No description provided.