Re: High traffic on this list, and Mozilla root program involvement

2017-08-15 Thread Kathleen Wilson via dev-security-policy
All, While I understand the desire to normally have one Bugzilla Bug per root cause per CA, I do not have the bandwidth to do this. So, I am going to create one bug per CA that I find in the recent m.d.s.policy posts, and list all of the problems pertaining to that CA in their bug. Thanks to

Re: High traffic on this list, and Mozilla root program involvement

2017-08-10 Thread Gervase Markham via dev-security-policy
Hi Jeremy, On 09/08/17 21:57, Jeremy Rowley wrote: > I was thinking you should just have the Cas add them all for you. Makes it > easier on you and demonstrates they are tracking and remediating these > issues. If I were going to create a bug for these in Mozilla would you > prefer to see one

RE: High traffic on this list, and Mozilla root program involvement

2017-08-09 Thread Jeremy Rowley via dev-security-policy
Of Gervase Markham via dev-security-policy Sent: Wednesday, August 9, 2017 9:34 AM To: mozilla-dev-security-pol...@lists.mozilla.org Subject: Re: High traffic on this list, and Mozilla root program involvement On 09/08/17 00:12, Jeremy Rowley wrote: > Do you want that added as a new bug for

Re: High traffic on this list, and Mozilla root program involvement

2017-08-09 Thread Gervase Markham via dev-security-policy
On 09/08/17 00:12, Jeremy Rowley wrote: > Do you want that added as a new bug for all the issues listed? I'm not sure I follow. Do I want what added? I will be filing any additional appropriate bugs when I get around to triaging all the messages in this forum. Gerv

RE: High traffic on this list, and Mozilla root program involvement

2017-08-08 Thread Jeremy Rowley via dev-security-policy
Do you want that added as a new bug for all the issues listed? -Original Message- From: dev-security-policy [mailto:dev-security-policy-bounces+jeremy.rowley=digicert.com@lists.mozilla .org] On Behalf Of Gervase Markham via dev-security-policy Sent: Tuesday, August 8, 2017 10:02 AM To: