-
Notifications
You must be signed in to change notification settings - Fork 577
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
allowing fscrypt files #3185
Comments
unsure whether helpful
|
Thanks, that works for me. I'll forward your suggestion and ask if that solves their problem. |
It looks like they are also using |
#!/bin/bash
private_home="$(mktemp -dt private-firejail-home.XXXXXX)"
firejail --allusers --private="$private_home" <program>
rm -rf "$private_home" NOTE: $private_home is visible for other programs (except |
Looks like the problem is actually with
With |
A Debian user reported probems with whitelisting and accessing fscrypt-related files from within firejail.
Especially /home/.fscrypt seems to be a problem, because only the user's home directory is available in /home, not any other directories/files.
Does anyone have an idea how this could be fixed?
The text was updated successfully, but these errors were encountered: