The CA/Browser Forum’s Bylaws at Section 2.3(c) allow the Forum Chair
(currently me) to invite Interested Parties to participate in Working Group
meetings.
I hereby extend an invitation to Forum Interested Parties to participate in
person or remotely in the all-day Validation Working Group
On Tuesday, May 24, 2016 at 2:01:22 PM UTC+2, Ryan Sleevi wrote:
> On Friday, May 20, 2016 at 10:24:56 AM UTC-7, Andrew Ayer wrote:
> > In fact, Kathleen asked explicitly for what the answers "should be" in
> > addition to what they are, so my email was not unrelated. To be more
> > explicit, I
On Friday, May 20, 2016 at 6:22:21 PM UTC-7, Peter Bowen wrote:
> [ Disclaimer: This message is my personal view and does not
> necessarily represent that of my employer. ]
>
> On Fri, May 20, 2016 at 5:41 PM, [Kirk Hall] wrote:
> > Peter -- the reference to BR 9.6.8(8) is interesting, but is
On Friday, May 20, 2016 at 2:09:42 AM UTC-7, Ben Laurie wrote:
> > 4.9.3. Procedure for Revocation Request
> >
> >"*** The CA SHALL provide Subscribers, Relying Parties, Application
> > Software Suppliers, and other third parties with clear instructions for
> > reporting suspected Private
Matt, that's a bit harsh, and you are all over the map. I was only responding
to Kathleen's questions, which asked what do the current BRs require CAs to do
when they receive reports of SSL certificates issued to malware injection
sites. I was not proposing any new rules or any new
Andrew - As I outlined in my message above, the BRs cover two distinct
situations: (1) when must CAs revoke certs that have already been issued for
“Certificate misuse, or other types of fraud, compromise, misuse, or
inappropriate conduct related to Certificates,” and (2) when CAs must refuse
On Tuesday, February 23, 2016 at 10:58:19 AM UTC-8, Gervase Markham wrote:
> Mozilla and other browsers have been approached by Worldpay, a large
> payment processor, via Symantec, their CA. They have been transitioning
> to SHA-2 but due to an oversight have failed to do so in time for a
>
On Tuesday, February 23, 2016 at 10:58:19 AM UTC-8, Gervase Markham wrote:
> Mozilla and other browsers have been approached by Worldpay, a large
> payment processor, via Symantec, their CA. They have been transitioning
> to SHA-2 but due to an oversight have failed to do so in time for a
>
8 matches
Mail list logo
