Re: Symantec Issues List

2017-04-02 Thread Peter Bowen via dev-security-policy
On Sun, Apr 2, 2017 at 9:36 PM, Ryan Sleevi wrote: > > On Sun, Apr 2, 2017 at 11:14 PM Peter Bowen via dev-security-policy > wrote: >> >> On Fri, Mar 31, 2017 at 11:39 AM, Gervase Markham via >> dev-security-policy wrote: >> > As we continue to consider how best to react to the most recent incid

Re: Symantec Issues List

2017-04-02 Thread Ryan Sleevi via dev-security-policy
On Sun, Apr 2, 2017 at 11:14 PM Peter Bowen via dev-security-policy < dev-security-policy@lists.mozilla.org> wrote: > On Fri, Mar 31, 2017 at 11:39 AM, Gervase Markham via > dev-security-policy wrote: > > As we continue to consider how best to react to the most recent incident > > involving Syman

Re: Symantec Issues List

2017-04-02 Thread Peter Bowen via dev-security-policy
On Fri, Mar 31, 2017 at 11:39 AM, Gervase Markham via dev-security-policy wrote: > As we continue to consider how best to react to the most recent incident > involving Symantec, and given that there is a question of whether it is > part of a pattern of behaviour, it seemed best to produce an issue

Re: Symantec Issues List

2017-04-02 Thread Peter Bowen via dev-security-policy
On Fri, Mar 31, 2017 at 11:39 AM, Gervase Markham via dev-security-policy wrote: > As we continue to consider how best to react to the most recent incident > involving Symantec, and given that there is a question of whether it is > part of a pattern of behaviour, it seemed best to produce an issue