Skip to content
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

Feature Request: Per profile 'disable-mnt' #1231

Closed
SkewedZeppelin opened this issue Apr 17, 2017 · 0 comments
Closed

Feature Request: Per profile 'disable-mnt' #1231

SkewedZeppelin opened this issue Apr 17, 2017 · 0 comments
Labels
enhancement New feature request

Comments

@SkewedZeppelin
Copy link
Collaborator

SkewedZeppelin commented Apr 17, 2017

A per profile 'disable-mnt' like the one configurable in firejail.conf would be super useful, especially for hardening profiles that are currently whitelist only. Like having a sandboxed program that can only access one dir in your home folder, but can still read/write to your other drives is a bit silly.

Like https://gist.github.com/SpotComms/385bf9f2290b51a2639dacedc74bb666 vs #1009, #1009 would've blocked a lot of programs from accessing files they should have access to, but this would just be for hardening already whitelist only profiles.

One issue I do see is that for instance I keep my downloads under /mnt/Drive-X/Temp/Downloads and have it symlinked in ~/, so having disable-mnt in Chromium/Firefox would break access to downloads. Having disable-mnt add a check that would keep that dir (the ones whitelisted in each profile) whitelisted but still blacklist all the other drives/paths would be nice.

@SkewedZeppelin SkewedZeppelin changed the title Feature Request: Per profile 'disable-mnt' and 'disable-sys' Feature Request: Per profile 'disable-mnt' Apr 17, 2017
@netblue30 netblue30 added the enhancement New feature request label Apr 17, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature request
Projects
None yet
Development

No branches or pull requests

2 participants