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

[Request] dont expose /home #184

Closed
biji opened this issue Mar 15, 2021 · 5 comments
Closed

[Request] dont expose /home #184

biji opened this issue Mar 15, 2021 · 5 comments
Assignees

Comments

@biji
Copy link

biji commented Mar 15, 2021

Is your feature request related to a problem? Please describe.

When running from flatpak, do not expose /home to protect from malwares

@mirkobrombin
Copy link
Member

You can change bottles permissions with Flatseal

@biji
Copy link
Author

biji commented Mar 15, 2021

Thanks, tried to remove xdg-* using Flatseal
It would be good for new option Sandbox mode to not linking My Documents, etc.

@mirkobrombin
Copy link
Member

It might be interesting but at the moment I want to focus on the main purpose of bottles and the development of v4, without adding too many other tasks.

@ManIVIctorious
Copy link

Since wine is often used to run production software instead of just games, this doesn't sound like a sane default configuration. If you would e.g. use bottles for microsoft office support, the applications would be rather useless without access to documents.

What could be done though, would be to make bubblewrap a dependency of the project and add a sandboxing gui, applicable to any environment/bottle. Unfortunately, I have no experience with bubblewrap inside a sandbox (although it should be possible since a little bit more than a year ago with recent flatpak versions), and therefore can't estimate how much work this would be.

@mirkobrombin
Copy link
Member

Ref: bottlesdevs/libbottles#1

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

No branches or pull requests

4 participants