[GH-ISSUE #1115] better self-explaining options (than --private) #763

Closed
opened 2026-05-05 06:36:27 -06:00 by gitea-mirror · 3 comments
Owner

Originally created by @testbird on GitHub (Feb 26, 2017).
Original GitHub issue: https://github.com/netblue30/firejail/issues/1115

firejail could make the meaning of its options much more clearer by providing a more self-explaining alternative. (e.g. the meaning of the --private options seems not very clear to me all the time.)

What would you think about a scheme along these lines:
--private could have more clearly named alternatives like this:

--persistent-home=/home/$USER (the default, make permanent changes to the settings)
--discardable-home=/home/$USER (starting with some existing settings)
--discardable-home (defaults to =$HOME)
--discardable-home=/home/$USER --home-whitelist=.directory,file,etc, (adding restrictions)
--discardable-home=empty (the legacy --private, resulting in starting with the programs default settings)

NB: Currently there seems to be an inconsistency:
--private provides a discardable version of an empty home, but
--private=own_subdir uses ~/own_subdir as persistent storage.

Originally created by @testbird on GitHub (Feb 26, 2017). Original GitHub issue: https://github.com/netblue30/firejail/issues/1115 firejail could make the meaning of its options much more clearer by providing a more self-explaining alternative. (e.g. the meaning of the --private options seems not very clear to me all the time.) What would you think about a scheme along these lines: --private could have more clearly named alternatives like this: --persistent-home=/home/$USER (the default, make permanent changes to the settings) --discardable-home=/home/$USER (starting with some existing settings) --discardable-home (defaults to =$HOME) --discardable-home=/home/$USER --home-whitelist=.directory,file,etc, (adding restrictions) --discardable-home=empty (the legacy --private, resulting in starting with the programs default settings) NB: Currently there seems to be an inconsistency: --private provides a *discardable* version of an empty home, but --private=own_subdir uses ~/own_subdir as *persistent* storage.
gitea-mirror 2026-05-05 06:36:27 -06:00
Author
Owner

@netblue30 commented on GitHub (Feb 28, 2017):

You are right, it is not consistent in this moment. It just evolved this way over time, and is kind of difficult to change it now. I'll look into it.

<!-- gh-comment-id:283052797 --> @netblue30 commented on GitHub (Feb 28, 2017): You are right, it is not consistent in this moment. It just evolved this way over time, and is kind of difficult to change it now. I'll look into it.
Author
Owner

@testbird commented on GitHub (Feb 28, 2017):

Ah, well, understandable! Good to know you keep the wording in mind.
Once it has matured you may add the new options as mutually exclusive to the old ones, and then use the new ones in explanations.

<!-- gh-comment-id:283190064 --> @testbird commented on GitHub (Feb 28, 2017): Ah, well, understandable! Good to know you keep the wording in mind. Once it has matured you may add the new options as mutually exclusive to the old ones, and then use the new ones in explanations.
Author
Owner

@netblue30 commented on GitHub (Mar 3, 2017):

Absolutely, it will go through a major cleanup before 1.0 release.

<!-- gh-comment-id:284051495 --> @netblue30 commented on GitHub (Mar 3, 2017): Absolutely, it will go through a major cleanup before 1.0 release.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/firejail#763
No description provided.