mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #708] Option to disable warnings/errors in production environments #485
Labels
No labels
LTS merge
LTS merge
bug
bug
converted-to-discussion
doc-todo
documentation
duplicate
enhancement
file-transfer
firecfg
firejail-in-firejail
firetools
graphics
help wanted
information_old
installation
invalid
modif
moved
needinfo
networking
notabug
notourbug
old-version
overlayfs
packaging
profile-request
pull-request
question
question_old
removal
runtime-permissions
sandbox-ipc
security
stale
wiki
wiki
wontfix
wordpress
workaround
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/firejail#485
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @nuxwin on GitHub (Aug 13, 2016).
Original GitHub issue: https://github.com/netblue30/firejail/issues/708
Hello,
We use FireJail to provide restricted login shells to our users with the
--chrootoption. When a user is connecting through SSH, the following warning is always shown:Also, other warnings (or errors) related to a misconfiguration (or any other problem) are always shown.
Those warnings (or errors) should be hidden in production environment where the end-users don't care about them (case of a shared hosting environment). Currently the only way to hide the warning shown above is to add the
--noprofileoption or by adding custom profile but this applies only to this warning.Please add an option to hide any warning and or error in production environments. Note that the
--quietoption has not effect.Thank you for your interest.
@netblue30 commented on GitHub (Aug 13, 2016):
It is a bug, this warning should go under --quiet. I'll bring in a fix shortly.
Probably there are more like it. The idea is to have only catastrophic things escaping quiet. Let me know if you run into anything else.
@nuxwin commented on GitHub (Aug 14, 2016):
Fixed in master. Thanks. I don't close that ticket because as you said, There is probably more issues like this. You're free to close that issue.
@netblue30 commented on GitHub (Aug 14, 2016):
All fixed, thanks for the bug.