Okay - could you also specify whether this applies going forward or whether 
all client/code signing certificates chained to a public intermediate that 
fails to comply will be affected?

-----Original Message-----
From: Gervase Markham [mailto:g...@mozilla.org]
Sent: Thursday, January 12, 2017 11:51 AM
To: Jeremy Rowley <jeremy.row...@digicert.com>; CA/Browser Forum Public 
Discussion List <public@cabforum.org>
Subject: Re: [cabfpub] Mozilla SHA-1 further restrictions (v4)

On 12/01/17 18:17, Jeremy Rowley wrote:
> Hey Gerv - when dos this policy take effect? Or is this being proposed
> for the next Mozilla policy update.

I am trying to nail the text down; we'd then decide a timeline, probably 
initially promulgate it via a CA Communication, and add it to our policy.

Gerv

Attachment: smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________
Public mailing list
Public@cabforum.org
https://cabforum.org/mailman/listinfo/public

Reply via email to