All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Lautrbach <plautrba@redhat.com>
To: SElinux list <selinux@vger.kernel.org>
Cc: Cristian Ariza <cariza@collaborative.li>,
	Stephen Smalley <stephen.smalley.work@gmail.com>,
	Ondrej Mosnacek <omosnace@redhat.com>
Subject: Re: No window opening when running sandbox -S
Date: Tue, 9 Jun 2020 20:03:37 +0200	[thread overview]
Message-ID: <20200609180337.GB139421@localhost.localdomain> (raw)
In-Reply-To: <7dd7daa7-217a-fc99-f7d7-d1c629f7c592@collaborative.li>

[-- Attachment #1: Type: text/plain, Size: 938 bytes --]

On Tue, Jun 09, 2020 at 06:17:40PM +0100, Cristian Ariza wrote:
> On 09/06/2020 18:07, Petr Lautrbach wrote:
> > Do you use X session or Wayland?
> 
> I've been doing tests now on [Xorg + XFCE] and [Wayland + Gnome]. What I
> could see is:
> 
> * Gnome: -S doesn't work, -X firefox seems fine
> * XFCE: -S works perfectly, -X firefox doesn't always work and I haven't
> really found what changes between when it works and when it doesn't.
> 
> 
> > Btw few years ago I wrote support for bubblewrap in sandbox so it's uses it
> > instead of seunshare [1] but I haven't finished it and sent for review.
> > 
> > https://github.com/bachradsusi/SELinuxProject-selinux/commit/5158ea1f552fc098647d4c503f646bdcb6d0737f
> 
> What benefits would bublewrap provide?
> 

I don't know. It should provide everything `sandbox` needs, and it's used in other projects while `seunshare` seems to be
written just for `sandbox`.




[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2020-06-09 18:03 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
2020-06-09 17:07   ` Petr Lautrbach
2020-06-09 17:17     ` Cristian Ariza
2020-06-09 18:03       ` Petr Lautrbach [this message]

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=20200609180337.GB139421@localhost.localdomain \
    --to=plautrba@redhat.com \
    --cc=cariza@collaborative.li \
    --cc=omosnace@redhat.com \
    --cc=selinux@vger.kernel.org \
    --cc=stephen.smalley.work@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.