Re: Fission Engineering Newsletter #1

2019-02-15 Thread Neha Kochar
>> Are you including bugs that are about reducing our memory usage
>> with more processes? What about doing better sandboxing of the content
>> process (e.g. ensuring a compromised process can't request information
>> from the parent that isn't relevant to it)?
> This is https://bugzilla.mozilla.org/show_bug.cgi?id=1505832
> Its major sub-bug that pertains specifically to IPC is
> https://bugzilla.mozilla.org/show_bug.cgi?id=fission-ipc

Yes, fission-origin-sandbox, fission-ipc and memshrink-content are all
important parts of Fission and we need to triage the associated sub-bugs
into appropriate Fission milestones. I'll reach out to you on a separate
thread.

Thanks,
Neha.
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


Re: Fission Engineering Newsletter #1

2019-02-13 Thread Matthew N.

On 2019-02-13 9:02 p.m., Tom Ritter wrote:

On Wed, Feb 13, 2019 at 9:48 PM Matthew N.  wrote:

What about doing better sandboxing of the content
process (e.g. ensuring a compromised process can't request information
from the parent that isn't relevant to it)?


This is https://bugzilla.mozilla.org/show_bug.cgi?id=1505832
Its major sub-bug that pertains specifically to IPC is
https://bugzilla.mozilla.org/show_bug.cgi?id=fission-ipc

For now, the focus on Fission is just getting it working, these
efforts (stronger sandboxing) will come after that.


I quoted the part about the milestone flag as I was wondering whether we 
are supposed to nominate such bugs now or we should only be nominating 
functional bugs? (Same goes for memory usage ones.)

___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


Re: Fission Engineering Newsletter #1

2019-02-13 Thread Tom Ritter
On Wed, Feb 13, 2019 at 9:48 PM Matthew N.  wrote:
> What about doing better sandboxing of the content
> process (e.g. ensuring a compromised process can't request information
> from the parent that isn't relevant to it)?

This is https://bugzilla.mozilla.org/show_bug.cgi?id=1505832
Its major sub-bug that pertains specifically to IPC is
https://bugzilla.mozilla.org/show_bug.cgi?id=fission-ipc

For now, the focus on Fission is just getting it working, these
efforts (stronger sandboxing) will come after that.

-tom
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


Re: Fission Engineering Newsletter #1

2019-02-13 Thread Matthew N.

On 2019-02-04 6:02 a.m., Nika Layzell wrote:

If have a bug which may be relevant to fission,*please*  let us know by
setting
the “Fission Milestone” project flag to ‘?’. We’ll swing by and triage it
into
the correct milestone.


It seems to me like there are a few overlapping areas in progress that 
are related but I'm not sure if they are now being tracked under one 
Fission umbrella… What types of bugs are considered part of the Fission 
project? Are you including bugs that are about reducing our memory usage 
with more processes? What about doing better sandboxing of the content 
process (e.g. ensuring a compromised process can't request information 
from the parent that isn't relevant to it)?


Thanks,
Matthew N.
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform