-
Notifications
You must be signed in to change notification settings - Fork 557
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
support all user readable directories (except cfg.homedir) in --private-home #1000
Comments
nocontext: and this is issue #1000 (yay!) |
@netblue30, please add this to the next release - this is a truly helpful feature. Couple of use cases are: allowing to use system-wide parts for homedir templates and using homedir parts from eCryptfs. |
I don't think this is in yet. @thewisenerd, please feel free to create a pull request (but base it off the current master, obviously haha) if you've already implemented this and we'll take a look there. Thanks! |
I found the
--private-home
option to be perfect for initializing a tmpfs$HOME
directory with a few files copied in, however, making it to read files only from user home top level directories is limiting for my use.I do not want to use the
--private=dir
option as changes made todir
from the sandboxed application are visible back in userspace. I do not also want, the hassles ofunshare
and creating a private tmpfs mount.example:
I want to initialize
$HOME
as private fs with a.config
directory, but I do not want to use my~/.config
directory, but another directory such as~/sandbox/.config
. Since fcopy takes the destination name fromstrrchr(fname, '/')
, the end result would be a.config
directory copied to$HOME/.config
nevertheless.ps: I have implemented this at thewisenerd@b548a7b and want to know if there's a better way to do this.
The text was updated successfully, but these errors were encountered: