From: Russell Coker <russell@coker.com.au>
To: Chris PeBenito <pebenito@ieee.org>
Cc: Jason Zaman <jason@perfinion.com>,
"selinux-refpolicy@vger.kernel.org"
<selinux-refpolicy@vger.kernel.org>
Subject: Re: [PATCH] s/mozilla/webbrowser/g
Date: Sun, 13 Jan 2019 11:50:01 +1100 [thread overview]
Message-ID: <3656424.1XRo0OdIgc@xev> (raw)
In-Reply-To: <9e966272-1e72-c250-bfb6-0f3b8bd07931@ieee.org>
On Sunday, 13 January 2019 6:46:44 AM AEDT Chris PeBenito wrote:
> The chromium policy Jason posted is indeed slimmer than the current
> mozilla policy (see Jason's thread), which would seem to indicate
> keeping them separate. However, the mozilla policy is so big because
> it's been around for a long time and has built up all of the various
> odds and ends that a browser brings in, which could possibly be missing
> from the chromium policy.
>
> I am on the fence. I could see going either way.
One of the things the Mozilla policy has is a domain for plugins while Chrome
has a domain for a sandbox. Does Chrome support running plugins in a separate
process (doesn't seem to but I generally avoid plugins). There seems to be
some real functionality difference between the two browsers.
--
My Main Blog http://etbe.coker.com.au/
My Documents Blog http://doc.coker.com.au/
prev parent reply other threads:[~2019-01-13 0:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-12 5:19 [PATCH] s/mozilla/webbrowser/g Russell Coker
2019-01-12 7:33 ` Jason Zaman
2019-01-12 19:46 ` Chris PeBenito
2019-01-12 22:55 ` Nicolas Iooss
2019-01-13 0:50 ` Russell Coker [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=3656424.1XRo0OdIgc@xev \
--to=russell@coker.com.au \
--cc=jason@perfinion.com \
--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 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.