[GH-ISSUE #2073] How does Firejail compared to Sandboxie #1401

Closed
opened 2026-05-05 08:03:46 -06:00 by gitea-mirror · 17 comments
Owner

Originally created by @Raj2032 on GitHub (Jul 30, 2018).
Original GitHub issue: https://github.com/netblue30/firejail/issues/2073

There is a Windows sandboxing application called 'Sandboxie' https://www.sandboxie.com. How does it differ to Firejail (other than limiting you that you can only sandbox one application at a time with the free version for Sandboxie)?

Originally created by @Raj2032 on GitHub (Jul 30, 2018). Original GitHub issue: https://github.com/netblue30/firejail/issues/2073 There is a Windows sandboxing application called 'Sandboxie' https://www.sandboxie.com. How does it differ to Firejail (other than limiting you that you can only sandbox one application at a time with the free version for Sandboxie)?
gitea-mirror 2026-05-05 08:03:46 -06:00
Author
Owner

@chiraag-nataraj commented on GitHub (Jul 30, 2018):

Here's a detailed comparison (--these are command-line arguments you can use for firejail):
Appearance Settings
Not currently in firejail (see #1983)

Recovery Settings
Usually done with --whitelist (for folders where you want to allow the program to see and write to) and --get to get files from other places within the sandbox. There are no exact analogues of these settings however (since firejail goes to sleep after launching the program).

Delete Settings
No exact analogue in firejail — all files created by the sandbox are deleted by default with the exception of stuff in --whitelisted directories. The command used to delete the sandbox is not configurable in firejail.

Program Start Settings
No analogue to Forced Folders settings. Forced Programs is similar to sudo firecfg, which sets it up so that all programs shipped with firejail profiles are automatically sandboxed by default. You can do this manually (i.e. for only certain programs) by doing sudo ln -s /usr/bin/firejail /usr/local/bin/<program name>.

Program Stop Settings
No analogue to these settings, but this has been an issue in the past (see #725).

File Migration Settings
No analogue to this setting. All files which are whitelisted will be copied over.

Restrictions Settings
Internet Access <-> --net=none, but --net is more powerful than that.
Start/Run Access <-> No clear analogue, but we have --private-bin, which functions in a similar way.
Drop Rights <-> --noroot, --nonewprivs
Other than these, there are far more options — --private-etc, --private-lib, --private-dev, --private-srv, --caps{,.drop,.keep}, --seccomp{,.block-secondary,.drop,.keep}, and so on. Check the manual page (man firejail) for more info.

Resource Access Settings
File Access > Direct Access & File Access > Full Access <-> --whitelist (the distinction doesn't apply in firejail).
File Access > Read-Only Access <-> --read-only.
File Access > Write-Only Access <-> No exact analogue, but can use judicious --whitelist commands to achieve a similar effect.
File Access > Blocked Access <-> --blacklist.
Registry Access doesn't apply.
IPC Access <-> --ipc-namespace
Window Access <-> Can kind of achieve a similar effect using --x11.
COM Access doesn't apply.

Applications Settings
This is basically a way to edit the profiles that are shipped with sandboxie, so you can do the same thing by editing the .profile files.

User Accounts Settings
Sandbox visibility is always restricted to the user who started it (as well as root) in firejail. You can also control who can start firejail sandboxes with /etc/firejail/firejail.users.

<!-- gh-comment-id:408875154 --> @chiraag-nataraj commented on GitHub (Jul 30, 2018): Here's a detailed comparison (`--these` are command-line arguments you can use for `firejail`): **Appearance Settings** Not currently in firejail (see #1983) **Recovery Settings** Usually done with `--whitelist` (for folders where you want to allow the program to see and write to) and `--get` to get files from other places within the sandbox. There are no exact analogues of these settings however (since `firejail` goes to sleep after launching the program). **Delete Settings** No exact analogue in `firejail` — all files created by the sandbox are deleted by default with the exception of stuff in `--whitelist`ed directories. The command used to delete the sandbox is not configurable in `firejail`. **Program Start Settings** No analogue to **Forced Folders** settings. **Forced Programs** is similar to `sudo firecfg`, which sets it up so that all programs shipped with `firejail` profiles are automatically sandboxed by default. You can do this manually (i.e. for only _certain_ programs) by doing `sudo ln -s /usr/bin/firejail /usr/local/bin/<program name>`. **Program Stop Settings** No analogue to these settings, but this has been an issue in the past (see #725). **File Migration Settings** No analogue to this setting. All files which are whitelisted will be copied over. **Restrictions Settings** **Internet Access** <-> `--net=none`, but `--net` is more powerful than that. **Start/Run Access** <-> No clear analogue, but we have `--private-bin`, which functions in a similar way. **Drop Rights** <-> `--noroot`, `--nonewprivs` Other than these, there are _far_ more options — `--private-etc`, `--private-lib`, `--private-dev`, `--private-srv`, `--caps{,.drop,.keep}`, `--seccomp{,.block-secondary,.drop,.keep}`, and so on. Check the manual page (`man firejail`) for more info. **Resource Access Settings** **File Access > Direct Access & File Access > Full Access** <-> `--whitelist` (the distinction doesn't apply in `firejail`). **File Access > Read-Only Access** <-> `--read-only`. **File Access > Write-Only Access** <-> No exact analogue, but can use judicious `--whitelist` commands to achieve a similar effect. **File Access > Blocked Access** <-> `--blacklist`. **Registry Access** doesn't apply. **IPC Access** <-> `--ipc-namespace` **Window Access** <-> Can kind of achieve a similar effect using `--x11`. **COM Access** doesn't apply. **Applications Settings** This is basically a way to edit the profiles that are shipped with `sandboxie`, so you can do the same thing by editing the `.profile` files. **User Accounts Settings** Sandbox visibility is _always_ restricted to the user who started it (as well as root) in `firejail`. You can also control _who_ can start `firejail` sandboxes with `/etc/firejail/firejail.users`.
Author
Owner

@Raj2032 commented on GitHub (Jul 30, 2018):

Thanks for your help, but there are some things I did not understand. "
firejail uses established technologies implemented at the kernel level"
What does that mean exactly? " Also, firejail lets you isolate things like
network stacks, which don't seem to be under the purview of sandboxie" I
thought that Sandboxie does allow users to disable an application from
being connected via the Internet?

On Tue, Jul 31, 2018 at 7:25 AM ಚಿರಾಗ್ ನಟರಾಜ್ notifications@github.com
wrote:

Closed #2073 https://github.com/netblue30/firejail/issues/2073.


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/netblue30/firejail/issues/2073#event-1761278702, or mute
the thread
https://github.com/notifications/unsubscribe-auth/Ab79BqO4kczdZDI6CF5rtpKOZ4eAxX2Yks5uL3njgaJpZM4Vlt46
.

<!-- gh-comment-id:409043403 --> @Raj2032 commented on GitHub (Jul 30, 2018): Thanks for your help, but there are some things I did not understand. " firejail uses established technologies implemented at the kernel level" What does that mean exactly? " Also, firejail lets you isolate things like network stacks, which don't seem to be under the purview of sandboxie" I thought that Sandboxie does allow users to disable an application from being connected via the Internet? On Tue, Jul 31, 2018 at 7:25 AM ಚಿರಾಗ್ ನಟರಾಜ್ <notifications@github.com> wrote: > Closed #2073 <https://github.com/netblue30/firejail/issues/2073>. > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <https://github.com/netblue30/firejail/issues/2073#event-1761278702>, or mute > the thread > <https://github.com/notifications/unsubscribe-auth/Ab79BqO4kczdZDI6CF5rtpKOZ4eAxX2Yks5uL3njgaJpZM4Vlt46> > . >
Author
Owner

@chiraag-nataraj commented on GitHub (Jul 30, 2018):

That's why I deleted my first comment and left the second comment (which is now the only comment) - I hadn't seen a whole bunch of configuration options in sandboxie earlier.

<!-- gh-comment-id:409043752 --> @chiraag-nataraj commented on GitHub (Jul 30, 2018): That's why I deleted my first comment and left the second comment (which is now the only comment) - I hadn't seen a whole bunch of configuration options in `sandboxie` earlier.
Author
Owner

@Raj2032 commented on GitHub (Jul 30, 2018):

Oh I didn't realise that you deleted your first comment as I am replying to
you via email.

Also one question, am I able to launch an application and it automatically
gets sandboxed with Firejail without having to launch the application
through firejail - so like I click on the shortcut of the application
through the DE and firejail automatically sandboxes the application?

On Tue, Jul 31, 2018 at 9:23 AM ಚಿರಾಗ್ ನಟರಾಜ್ notifications@github.com
wrote:

That's why I deleted my first comment and left the second comment (which
is now the only comment) - I hadn't seen a whole bunch of configuration
options in sandboxie earlier.


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/netblue30/firejail/issues/2073#issuecomment-409043752,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Ab79Bi5qLeMH2hVKeBJQ19jyu4XQfqGiks5uL5VWgaJpZM4Vlt46
.

<!-- gh-comment-id:409044221 --> @Raj2032 commented on GitHub (Jul 30, 2018): Oh I didn't realise that you deleted your first comment as I am replying to you via email. Also one question, am I able to launch an application and it automatically gets sandboxed with Firejail without having to launch the application through firejail - so like I click on the shortcut of the application through the DE and firejail automatically sandboxes the application? On Tue, Jul 31, 2018 at 9:23 AM ಚಿರಾಗ್ ನಟರಾಜ್ <notifications@github.com> wrote: > That's why I deleted my first comment and left the second comment (which > is now the only comment) - I hadn't seen a whole bunch of configuration > options in sandboxie earlier. > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <https://github.com/netblue30/firejail/issues/2073#issuecomment-409043752>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/Ab79Bi5qLeMH2hVKeBJQ19jyu4XQfqGiks5uL5VWgaJpZM4Vlt46> > . >
Author
Owner

@chiraag-nataraj commented on GitHub (Jul 30, 2018):

Yes. You can use firecfg for that. Or, if you don't want to automatically sandbox all supported applications, you can do something like sudo ln -s /usr/bin/firejail /usr/local/bin/<program name>.

<!-- gh-comment-id:409044636 --> @chiraag-nataraj commented on GitHub (Jul 30, 2018): Yes. You can use `firecfg` for that. Or, if you don't want to automatically sandbox _all_ supported applications, you can do something like `sudo ln -s /usr/bin/firejail /usr/local/bin/<program name>`.
Author
Owner

@Raj2032 commented on GitHub (Jul 30, 2018):

Oh ok thanks for that :)

Does firejail reduce the program's performance, and can malicious program
break through the firejail's security and compremise the entire OS if
possible?

On Tue, Jul 31, 2018 at 9:27 AM ಚಿರಾಗ್ ನಟರಾಜ್ notifications@github.com
wrote:

Yes. You can use firecfg for that. Or, if you don't want to automatically
sandbox all supported applications, you can do something like sudo ln
-s /usr/bin/firejail /usr/local/bin/.


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/netblue30/firejail/issues/2073#issuecomment-409044636,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Ab79BjjjOrW8C3cMPgp5D4UaXUwzEr6Qks5uL5Z1gaJpZM4Vlt46
.

<!-- gh-comment-id:409045827 --> @Raj2032 commented on GitHub (Jul 30, 2018): Oh ok thanks for that :) Does firejail reduce the program's performance, and can malicious program break through the firejail's security and compremise the entire OS if possible? On Tue, Jul 31, 2018 at 9:27 AM ಚಿರಾಗ್ ನಟರಾಜ್ <notifications@github.com> wrote: > Yes. You can use firecfg for that. Or, if you don't want to automatically > sandbox *all* supported applications, you can do something like sudo ln > -s /usr/bin/firejail /usr/local/bin/<program name>. > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <https://github.com/netblue30/firejail/issues/2073#issuecomment-409044636>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/Ab79BjjjOrW8C3cMPgp5D4UaXUwzEr6Qks5uL5Z1gaJpZM4Vlt46> > . >
Author
Owner

@chiraag-nataraj commented on GitHub (Jul 30, 2018):

Does firejail reduce the program's performance, and can malicious program break through the firejail's security and compremise the entire OS if possible?

No, firejail doesn't (generally) reduce the program's performance. Pretty much everything firejail uses is actually stuff implemented by the kernel (namespaces, seccomp-bpf, capabilities, etc). Nothing is perfect, so yes, something could defeat firejail's isolation techniques. But at that point, since the techniques are things enforced by the kernel, you have bigger issues on your hands.

Fundamentally, nothing is perfect, and security is about layers - building layers of security such that you don't depend on any one layer too much. For example, you could do firejail + apparmor + regular UNIX permissions, in which case someone would have to defeat the isolation techniques employed by firejail and apparmor, as well as somehow find a way to gain root. The more you add, the harder it becomes for someone to break through, realistically speaking.

<!-- gh-comment-id:409046855 --> @chiraag-nataraj commented on GitHub (Jul 30, 2018): > Does firejail reduce the program's performance, and can malicious program break through the firejail's security and compremise the entire OS if possible? No, `firejail` doesn't (generally) reduce the program's performance. Pretty much everything `firejail` uses is actually stuff implemented by the kernel (namespaces, seccomp-bpf, capabilities, etc). Nothing is perfect, so yes, something could defeat firejail's isolation techniques. But at that point, since the techniques are things enforced by the _kernel_, you have bigger issues on your hands. Fundamentally, nothing is perfect, and security is about layers - building layers of security such that you don't depend on any one layer too much. For example, you could do `firejail` + `apparmor` + regular UNIX permissions, in which case someone would have to defeat the isolation techniques employed by `firejail` _and_ `apparmor`, as well as somehow find a way to gain root. The more you add, the harder it becomes for someone to break through, realistically speaking.
Author
Owner

@Raj2032 commented on GitHub (Jul 30, 2018):

Oh I see, thanks for your help then.

On Tue, Jul 31, 2018 at 9:40 AM ಚಿರಾಗ್ ನಟರಾಜ್ notifications@github.com
wrote:

Does firejail reduce the program's performance, and can malicious program
break through the firejail's security and compremise the entire OS if
possible?

No, firejail doesn't (generally) reduce the program's performance. Pretty
much everything firejail uses is actually stuff implemented by the kernel
(namespaces, seccomp-bpf, capabilities, etc). Nothing is perfect, so yes,
something could defeat firejail's isolation techniques. But at that point,
since the techniques are things enforced by the kernel, you have bigger
issues on your hands.

Fundamentally, nothing is perfect, and security is about layers - building
layers of security such that you don't depend on any one layer too much.
For example, you could do firejail + apparmor + regular UNIX permissions,
in which case someone would have to defeat the isolation techniques
employed by firejail and apparmor, as well as somehow find a way to
gain root. The more you add, the harder it becomes for someone to break
through, realistically speaking.


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/netblue30/firejail/issues/2073#issuecomment-409046855,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Ab79BrAljOQT-qFklJRlcRjPaR1TUGVIks5uL5l8gaJpZM4Vlt46
.

<!-- gh-comment-id:409048004 --> @Raj2032 commented on GitHub (Jul 30, 2018): Oh I see, thanks for your help then. On Tue, Jul 31, 2018 at 9:40 AM ಚಿರಾಗ್ ನಟರಾಜ್ <notifications@github.com> wrote: > Does firejail reduce the program's performance, and can malicious program > break through the firejail's security and compremise the entire OS if > possible? > > No, firejail doesn't (generally) reduce the program's performance. Pretty > much everything firejail uses is actually stuff implemented by the kernel > (namespaces, seccomp-bpf, capabilities, etc). Nothing is perfect, so yes, > something could defeat firejail's isolation techniques. But at that point, > since the techniques are things enforced by the *kernel*, you have bigger > issues on your hands. > > Fundamentally, nothing is perfect, and security is about layers - building > layers of security such that you don't depend on any one layer too much. > For example, you could do firejail + apparmor + regular UNIX permissions, > in which case someone would have to defeat the isolation techniques > employed by firejail *and* apparmor, as well as somehow find a way to > gain root. The more you add, the harder it becomes for someone to break > through, realistically speaking. > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <https://github.com/netblue30/firejail/issues/2073#issuecomment-409046855>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/Ab79BrAljOQT-qFklJRlcRjPaR1TUGVIks5uL5l8gaJpZM4Vlt46> > . >
Author
Owner

@chiraag-nataraj commented on GitHub (Jul 30, 2018):

No problem!

<!-- gh-comment-id:409048208 --> @chiraag-nataraj commented on GitHub (Jul 30, 2018): No problem!
Author
Owner

@Raj2032 commented on GitHub (Jul 30, 2018):

Are you the owner of Firejail?

On Tue, Jul 31, 2018 at 9:49 AM ಚಿರಾಗ್ ನಟರಾಜ್ notifications@github.com
wrote:

No problem!


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/netblue30/firejail/issues/2073#issuecomment-409048208,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Ab79BkTrHI-GVAnlakbzUlAHWFGp3ND7ks5uL5t0gaJpZM4Vlt46
.

<!-- gh-comment-id:409048585 --> @Raj2032 commented on GitHub (Jul 30, 2018): Are you the owner of Firejail? On Tue, Jul 31, 2018 at 9:49 AM ಚಿರಾಗ್ ನಟರಾಜ್ <notifications@github.com> wrote: > No problem! > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <https://github.com/netblue30/firejail/issues/2073#issuecomment-409048208>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/Ab79BkTrHI-GVAnlakbzUlAHWFGp3ND7ks5uL5t0gaJpZM4Vlt46> > . >
Author
Owner

@chiraag-nataraj commented on GitHub (Jul 30, 2018):

No. I've contributed a bit of code, but @netblue30 "owns" firejail, I suppose.

<!-- gh-comment-id:409049085 --> @chiraag-nataraj commented on GitHub (Jul 30, 2018): No. I've contributed a bit of code, but @netblue30 "owns" firejail, I suppose.
Author
Owner

@Raj2032 commented on GitHub (Jul 30, 2018):

Oh I see, is it written in C++?

On Tue, Jul 31, 2018 at 9:54 AM ಚಿರಾಗ್ ನಟರಾಜ್ notifications@github.com
wrote:

No. I've contributed a bit of code, but @netblue30
https://github.com/netblue30 "owns" firejail, I suppose.


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/netblue30/firejail/issues/2073#issuecomment-409049085,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Ab79Btdtj_XTjc3xMQkUwQp1FY5cLhGMks5uL5ypgaJpZM4Vlt46
.

<!-- gh-comment-id:409049588 --> @Raj2032 commented on GitHub (Jul 30, 2018): Oh I see, is it written in C++? On Tue, Jul 31, 2018 at 9:54 AM ಚಿರಾಗ್ ನಟರಾಜ್ <notifications@github.com> wrote: > No. I've contributed a bit of code, but @netblue30 > <https://github.com/netblue30> "owns" firejail, I suppose. > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <https://github.com/netblue30/firejail/issues/2073#issuecomment-409049085>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/Ab79Btdtj_XTjc3xMQkUwQp1FY5cLhGMks5uL5ypgaJpZM4Vlt46> > . >
Author
Owner

@chiraag-nataraj commented on GitHub (Jul 31, 2018):

It's written in C.

<!-- gh-comment-id:409069662 --> @chiraag-nataraj commented on GitHub (Jul 31, 2018): It's written in C.
Author
Owner

@Raj2032 commented on GitHub (Jul 31, 2018):

Just asking out of curosity why did you guys decide to use C over C++?
Cause I heard that with C++ you can use C features and do everything
manually without using the automated features??

On Tue, Jul 31, 2018 at 12:05 PM ಚಿರಾಗ್ ನಟರಾಜ್ notifications@github.com
wrote:

It's written in C.


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/netblue30/firejail/issues/2073#issuecomment-409069662,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Ab79BtZV5EMMYMNR4g0dkLHCUrL5fsc0ks5uL7tlgaJpZM4Vlt46
.

<!-- gh-comment-id:409070698 --> @Raj2032 commented on GitHub (Jul 31, 2018): Just asking out of curosity why did you guys decide to use C over C++? Cause I heard that with C++ you can use C features and do everything manually without using the automated features?? On Tue, Jul 31, 2018 at 12:05 PM ಚಿರಾಗ್ ನಟರಾಜ್ <notifications@github.com> wrote: > It's written in C. > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <https://github.com/netblue30/firejail/issues/2073#issuecomment-409069662>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/Ab79BtZV5EMMYMNR4g0dkLHCUrL5fsc0ks5uL7tlgaJpZM4Vlt46> > . >
Author
Owner

@chiraag-nataraj commented on GitHub (Jul 31, 2018):

I didn't make that decision. These questions are better answered by @netblue30.

<!-- gh-comment-id:409074407 --> @chiraag-nataraj commented on GitHub (Jul 31, 2018): I didn't make that decision. These questions are better answered by @netblue30.
Author
Owner

@Raj2032 commented on GitHub (Jul 31, 2018):

Thanks for that, does he normally respond if you guys tag him?

On Tue, Jul 31, 2018 at 12:34 PM ಚಿರಾಗ್ ನಟರಾಜ್ notifications@github.com
wrote:

I didn't make that decision. These questions are better answered by
@netblue30 https://github.com/netblue30.


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/netblue30/firejail/issues/2073#issuecomment-409074407,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Ab79BlP0jBCF3qSpC-48XUEteUH1BB-4ks5uL8I3gaJpZM4Vlt46
.

<!-- gh-comment-id:409120365 --> @Raj2032 commented on GitHub (Jul 31, 2018): Thanks for that, does he normally respond if you guys tag him? On Tue, Jul 31, 2018 at 12:34 PM ಚಿರಾಗ್ ನಟರಾಜ್ <notifications@github.com> wrote: > I didn't make that decision. These questions are better answered by > @netblue30 <https://github.com/netblue30>. > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <https://github.com/netblue30/firejail/issues/2073#issuecomment-409074407>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/Ab79BlP0jBCF3qSpC-48XUEteUH1BB-4ks5uL8I3gaJpZM4Vlt46> > . >
Author
Owner

@chiraag-nataraj commented on GitHub (Jul 31, 2018):

Depending on the issue. I think this issue has strayed far from where it started off, and these questions should be resolved either by reading the FAQ and other material on the website (https://firejail.wordpress.com) or, if that doesn't answer your question, contacting netblue directly.

<!-- gh-comment-id:409176901 --> @chiraag-nataraj commented on GitHub (Jul 31, 2018): Depending on the issue. I think this issue has strayed far from where it started off, and these questions should be resolved either by reading the FAQ and other material on the website (https://firejail.wordpress.com) or, if that doesn't answer your question, contacting netblue directly.
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#1401
No description provided.