On Thu, Mar 15, 2012 at 3:26 AM, Chris Jones wrote:
> That's right: the ideal model is one process per "app" and one process per
> (arbitrary web content).
processes (fork) are not secure, and are not securable. privilege
escalation is still possible. for maximum security (even when not
usin
; , dev-security@lists.mozilla.org,
> "Mozilla B2G mailing list"
>
> Sent: Tuesday, March 13, 2012 2:59:47 PM
> Subject: Re: [b2g] B2G's kernel level permissions and reliability
>
> So my understanding is that the goal would be one process per app,
> however for pe
So my understanding is that the goal would be one process per app, however for
performance reasons, apps may need to be grouped. There will always be at least
one lower-privileged process for running content (apps) and ideally there would
be at least enough to separate critical apps (dialer, sms
On 03/07/2012 08:11 PM, Chris Jones wrote:
>> Note that the solution is likely to be electrolysis, but, while it's
>> on
>> the roadmap, as far as I understand, it is likely that B2G won't
>> actually ship with electrolysis enabled, nor would it really be
>> planned
>> in the future.
>
> I'm not s
- Original Message -
> From: "Guillaume Destuynder"
> To: "Mozilla B2G mailing list"
> Cc: dev-security@lists.mozilla.org
> Sent: Wednesday, March 7, 2012 11:18:41 AM
> Subject: [b2g] B2G's kernel level permissions and reliability
>
> Note
