> I believe Root programs have the necessary policy in place to treat 
> incidents -in exceptional circumstances- on a case-by-case basis. Wayne 
> had mentioned in a previous post [4] that Mozilla doesn't want to be 
> responsible for assessing the potential impact, but that statement took 
> for granted that there was a definite violation of a requirement.

It looks like it would be useful to have this exceptions handling procedure in 
place, especially for situations like the current one with with low security 
impact but a high potential for producing service disruption everywhere.

Is Mozilla reassessing to introduce a procedure to handle exceptions?.
_______________________________________________
dev-security-policy mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-security-policy
            • Re: ... Ryan Sleevi via dev-security-policy
            • Re: ... Dimitris Zacharopoulos via dev-security-policy
            • Re: ... Tomas Gustavsson via dev-security-policy
            • Re: ... Ryan Sleevi via dev-security-policy
            • Re: ... James Burton via dev-security-policy
            • Re: ... Wayne Thayer via dev-security-policy
            • Re: ... Daymion Reynolds via dev-security-policy
            • Re: ... Ryan Sleevi via dev-security-policy
            • Re: ... Daymion Reynolds via dev-security-policy
            • Re: ... Peter Bowen via dev-security-policy
            • Re: ... Jaime Hablutzel via dev-security-policy
            • Re: ... Jaime Hablutzel via dev-security-policy
        • Re: EJBCA def... bif via dev-security-policy
          • Re: EJBCA... Matthew Hardeman via dev-security-policy
            • Re: ... Matt Palmer via dev-security-policy
            • Re: ... Matthew Hardeman via dev-security-policy
            • Re: ... Peter Gutmann via dev-security-policy
            • Re: ... okaphone.elektronika--- via dev-security-policy
      • Re: EJBCA default... Mike Kushner via dev-security-policy
  • The current and future rol... Jakob Bohm via dev-security-policy

Reply via email to