All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Smalley <stephen.smalley.work@gmail.com>
To: Cristian Ariza <cariza@collaborative.li>,
	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 09:02:08 -0400	[thread overview]
Message-ID: <CAEjxPJ4Rw-B00FWjpTL3dWLwJ8daqy6NH_7su-EtAXYky8caQA@mail.gmail.com> (raw)
In-Reply-To: <7b738730-bbc3-eb04-b8b8-63706cebce24@collaborative.li>

On Tue, Jun 9, 2020 at 4:05 AM Cristian Ariza <cariza@collaborative.li> wrote:
>
> $ sandbox -H sandbox/home -T sandbox/tmp -S
>
> shows a few Gtk warnings (which I am assuming means Gnome loaded
> somewhere) but no window opens. In the man page I can't find much
> information about how sandbox -S actually works so not sure if I am
> missing something or it's just a bug.
>
> I am using Fedora 32 with Gnome.

You are using sandbox as packaged by Fedora in
policycoreutils-sandbox?  If so, please file a bug against their
package.
To be honest, I don't use sandbox myself and I am not sure it is being
very well maintained these days.  It was originally created by Red
Hat.
It seems like it has been OBE by other efforts to sandbox apps on
Linux e.g. flatpak or snaps although I don't know that any of those
are leveraging SELinux.  I'd be tempted to remove it upstream unless
it is getting proper care and feeding.

  reply	other threads:[~2020-06-09 13:02 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 [this message]
2020-06-09 14:05   ` Cristian Ariza
2020-06-09 15:04     ` Topi Miettinen
2020-06-09 16:05       ` Cristian Ariza
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=CAEjxPJ4Rw-B00FWjpTL3dWLwJ8daqy6NH_7su-EtAXYky8caQA@mail.gmail.com \
    --to=stephen.smalley.work@gmail.com \
    --cc=cariza@collaborative.li \
    --cc=omosnace@redhat.com \
    --cc=plautrba@redhat.com \
    --cc=selinux@vger.kernel.org \
    /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.