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

add --private-template=directory option #681

Merged
merged 5 commits into from Aug 4, 2016

Conversation

Projects
None yet
2 participants
@nextime
Contributor

nextime commented Aug 4, 2016

--private mount a tmpfs over the user home, so, things like browser extensions and configurations are back to the defaults and you cannot pre-configure it easily.

--private=directory, on the other side, make the user home persistent.

--private-template=directory aim to /opt/firejail/templates/usernamebe an alternative, it act like --private mounting a tmpfs over the user home, and then it copy recursively all the files and dirs from a template directory to the created empty user home.

This way you can put, for example, a preconfigured .config/cromium directory let's says in /opt/firejail/templates/username, and then use
firejail --private-template=/opt/firejail/templates/username cromium

NOTE: as the copy from template is done after mounting the tmpfs to mask the user home, the template directory cannot be copied from inside the original user home.

@netblue30 netblue30 merged commit bf84057 into netblue30:master Aug 4, 2016

@netblue30

This comment has been minimized.

Owner

netblue30 commented Aug 4, 2016

Merged, thanks for the patch. I used to have this feature a long time ago and scrapped it. I will rename it private-home.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment