selinux-refpolicy.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Russell Coker <russell@coker.com.au>
To: Chris PeBenito <pebenito@ieee.org>
Cc: selinux-refpolicy@vger.kernel.org
Subject: Re: [PATCH] chrome/chromium
Date: Thu, 10 Jan 2019 16:17:54 +1100	[thread overview]
Message-ID: <11639347.phjdDo44MW@xev> (raw)
In-Reply-To: <f4be7e95-9b5d-985d-3033-6faec99e2742@ieee.org>

On Thursday, 10 January 2019 11:06:23 AM AEDT Chris PeBenito wrote:
> > allow $2 mozilla_t:fd use;
> > allow $2 mozilla_t:shm rw_shm_perms;
> > +       allow chrome_sandbox_t $2:fd use;
> > +       allow chrome_sandbox_t $2:fifo_file write;
> > +       allow chrome_sandbox_t $3:chr_file { read write };
> 
> Beyond that, this simply won't fly because all the seemingly conflicting
> types.  A user might think, "what does mozilla have to do with chrome? I
> don't even have mozilla installed!"  For this to work, we'd have to go
> down a generic browser policy, with correspondingly generic type names.
> I'm not opposed to this, but that'd be the first step.

Fair point.  Would you like me to submit a patch s/mozilla/webbrowser/g as the 
first step towards this?

-- 
My Main Blog         http://etbe.coker.com.au/
My Documents Blog    http://doc.coker.com.au/


  parent reply	other threads:[~2019-01-10  5:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-08  8:49 [PATCH] chrome/chromium Russell Coker
2019-01-10  0:06 ` Chris PeBenito
2019-01-10  1:11   ` Jason Zaman
2019-01-10  5:11     ` Russell Coker
2019-01-10  5:17   ` Russell Coker [this message]
2019-01-11  1:17     ` Chris PeBenito

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=11639347.phjdDo44MW@xev \
    --to=russell@coker.com.au \
    --cc=pebenito@ieee.org \
    --cc=selinux-refpolicy@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).