-
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
no way to selectively disable quiet-by-default in firejail.config #3125
Labels
enhancement
New feature request
Comments
Something like For everyone with the same problem and a newer firejail version. Since 0.9.60 it is possible to set |
Is there a description of firejail env vars somewhere? |
No.
|
netblue30
added a commit
that referenced
this issue
May 30, 2021
Fixed! More fixes coming, tracking them in #4275. |
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There is no way to re-enable firejail output once
quiet-by-default yes
is in /etc/firejail/firejail.config.I have
quiet-by-default yes
in my firejail.config so that profiles I have tested don't pollute my .xesssion-errors file. Unfortunately, there doesn't seem to be a way to re-enable verbose output for testing new profiles, short of editing firejail.config each time. I tried--ignore=quiet
,--ignore=quiet-by-default
, etc. with nothing working. Hence "quiet-by-default" is a bit of a misnomer.As an alternative to
quiet-by-default yes
, I tried puttingquiet
in globals.local, but that still allows a few lines of output to get into .xsession-errors when starting up jails in ways other than the command line. BTW - I use firecfg, so I can't easily put--quiet
on every firejail command line.I recommend having a separate configuration for firejail when started via firecfg symlink vs. when started manually. Alternatively, add a
--config=file
command-line option to firejail - although that might violate security in multi-user environments.I'm using firejail 0.9.58.2 in Debian buster.
The text was updated successfully, but these errors were encountered: