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

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

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

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

Fission Engineering Newsletter #1

2019-02-04 Thread Nika Layzell
*NOTE* This newsletter is also posted at https://mystor.github.io/fission-news-1.html *TL;DR* Fission is happening and our first “Milestone” is targeted at the end of February. Please file bugs related to fission and mark them as “Fission Milestone: ?” so we can triage them into the correct