[GH-ISSUE #708] Option to disable warnings/errors in production environments #485

Closed
opened 2026-05-05 05:57:07 -06:00 by gitea-mirror · 3 comments
Owner

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 --chroot option. When a user is connecting through SSH, the following warning is always shown:

Warning: default profile disabled by --chroot option

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 --noprofile option 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 --quiet option has not effect.

Thank you for your interest.

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 `--chroot` option. When a user is connecting through SSH, the following warning is always shown: ``` Warning: default profile disabled by --chroot option ``` 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 `--noprofile` option 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 `--quiet` option has not effect. Thank you for your interest.
gitea-mirror 2026-05-05 05:57:07 -06:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@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.

<!-- gh-comment-id:239630734 --> @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.
Author
Owner

@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.

<!-- gh-comment-id:239655622 --> @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.
Author
Owner

@netblue30 commented on GitHub (Aug 14, 2016):

All fixed, thanks for the bug.

<!-- gh-comment-id:239669794 --> @netblue30 commented on GitHub (Aug 14, 2016): All fixed, thanks for the bug.
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#485
No description provided.