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] Add file-access firewalling #657

Open
BillDietrich opened this issue Apr 26, 2022 · 4 comments
Open

[Feature Request] Add file-access firewalling #657

BillDietrich opened this issue Apr 26, 2022 · 4 comments
Labels
feature a whole new feature

Comments

@BillDietrich
Copy link

Summary:

Please add support for rules to control file access instead of network access. And support good regex on the file path specification.

For example, I'd like a rule that says "deny always Firefox access to any files outside home/Downloads and home/.mozilla" (on Linux).

@BillDietrich BillDietrich added the feature a whole new feature label Apr 26, 2022
@gustavo-iniguez-goya
Copy link
Collaborator

Hi @BillDietrich ,

I think this feature is out of scope of OpenSnitch. Personally I'd run Firefox/Chromium/etc sandboxed, with firejail for example.
It allows you run an application isolated from your filesystem: https://firejail.wordpress.com/documentation-2/basic-usage/#filesystem

@BillDietrich
Copy link
Author

I agree this would stretch the scope of OpenSnitch. But it seems it would fit fairly naturally into the existing OpenSnitch structure and UI. Just a new type of rule, and a different set of BPF hooks (I don't know much about that).

I have used Firejail and AppArmor and SELinux and various other mechanisms. But doing it in OpenSnitch would mean one GUI for both types of activity, one place to control network and file activity of application X. Convenient for users.

Please keep this request open and think about it, let's see if anyone else comments. Thanks.

@gustavo-iniguez-goya
Copy link
Collaborator

@wrouesnel
Copy link

I'd like to add a +1 to this but with a twist: what I'd really like to be able to do is redirect some types of file access requests. The use-case would be for a related feature #437 : for a big category of applications, what I want to do is inject MITM certificates - i.e. when using something like mitmproxy - without making system-wide changes or applying such changes globally.

So the ideal model would be setting rules which can remap which file gets opened by a request based on context, and pair that with a rule which will force the connection out through a proxy transparently.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature a whole new feature
Projects
None yet
Development

No branches or pull requests

3 participants