From: Cristian Ariza <cariza@collaborative.li>
To: Topi Miettinen <toiwoton@gmail.com>,
Stephen Smalley <stephen.smalley.work@gmail.com>,
Petr Lautrbach <plautrba@redhat.com>,
Ondrej Mosnacek <omosnace@redhat.com>
Cc: SElinux list <selinux@vger.kernel.org>
Subject: Re: No window opening when running sandbox -S
Date: Tue, 9 Jun 2020 17:05:39 +0100 [thread overview]
Message-ID: <3e5daa46-b775-4cdf-05a6-3339852d62cc@collaborative.li> (raw)
In-Reply-To: <61832df5-4aba-dacd-644b-b8e8eead0fe9@gmail.com>
On 09/06/2020 16:04, Topi Miettinen wrote:
> Please report Firejail issues on Github so they may get attention.
> Current (unreleased) Firejail also supports SELinux labeling, so
> existing SELinux rules apply even if the file system is heavily
> manipulated.
Is the opinion around the SELinux community that Firejail is good enough
(in the field of single-command GUI isolation)? A bit hesitant about its
security because of [1]. I know there is a few alternatives [2][3][4]
but I don't think I have the knowledge to actually judge which one
provides better isolation.
[1] https://www.whonix.org/wiki/Dev/Firejail#Security
[1] https://github.com/google/nsjail
[2] https://github.com/containers/bubblewrap
[3] https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html
next prev parent reply other threads:[~2020-06-09 16:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-09 7:53 No window opening when running sandbox -S Cristian Ariza
2020-06-09 13:02 ` Stephen Smalley
2020-06-09 14:05 ` Cristian Ariza
2020-06-09 15:04 ` Topi Miettinen
2020-06-09 16:05 ` Cristian Ariza [this message]
2020-06-09 17:07 ` Petr Lautrbach
2020-06-09 17:17 ` Cristian Ariza
2020-06-09 18:03 ` Petr Lautrbach
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3e5daa46-b775-4cdf-05a6-3339852d62cc@collaborative.li \
--to=cariza@collaborative.li \
--cc=omosnace@redhat.com \
--cc=plautrba@redhat.com \
--cc=selinux@vger.kernel.org \
--cc=stephen.smalley.work@gmail.com \
--cc=toiwoton@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.