Dear Mr Christoph Klein,
>>* V Clause (X): We analyzed this problem and found an issue, where the
>>variable wasn't transfered into the final certificate. This bug has been
>>around since our first issued EV certificate and wasn't noticed until now.
>>The problem is fixed, new certificates will
ail to align the EV profile for 5 years?
Best
J
El martes, 9 de febrero de 2016, 13:24:29 (UTC+1), Erwann Abalea escribió:
> Bonjour,
>
> Le mardi 9 février 2016 10:47:16 UTC+1, Jesus F a écrit :
> > Dear all,
> >
> > As A-Trust request EV treatment, I c
Dear all,
As A-Trust request EV treatment, I checked the EV issued certificates from
a-sign-SSL-EV-05 subordinate in ctr.sh (https://crt.sh/?Identity=%25&iCAID=6096)
ALL of them states in businessCategory the following text "V1.0, Clause 5.(X)".
This text is similar to what permitted by EV gui
Dear Mozilla community,
Reviewing the BR audit report of Comsign Ltd I have a few doubts regarding the
audits accepted by Mozilla and may someone can help me.
The BR audit was conducted according to the WebTrust forCertification
Authorites - SSL Baseline Requirements Audit Criteria version 1.1
Dear All,
Thanks Peter for your clarification but I think I haven't explained myself
properly.
My concern is not about that both CRL has the same CRL number (due they are
from different hierarchies). My concern is about how the CRL number is treated
by WoSign and how this number is increased. A
Dear WoSign and Mozilla community,
The CRL downloaded on june 29th from http://crls8.wosign.com/ca8-ssl4.crl (CRL
distribution point in https://root5evtest.wosign.com certificate) has a CRL
number of "00".
It also applies for the CRL downloaded on the same date from
http://crls6.wosign.com/ca6-
Regards,
>
> Volkan Nergiz
> TURKTRUST, Inc.
>
> -Original Message-----
> From: dev-security-policy
> [mailto:dev-security-policy-bounces+volkan.nergiz=turktrust.com...@lists.mozilla.org]
> On Behalf Of Jesus F
> Sent: Tuesday, March 3, 2015 6:28 PM
> To: mozilla-de
Hi all,
After some quick test of the OCSP Service I detect the following issues related
to the conformity with CA/Browser Forum Baseline Requirements for the Issuance
and Management of Publicly-Trusted Certificates (hereinafter BR) as required by
section 12 of Mozilla CA Certificate Inclusion
After some quick test of the OCSP Service I detect the following issues related
to the conformity with CA/Browser Forum Baseline Requirements for the Issuance
and Management of Publicly-Trusted Certificates (hereinafter BR) as required by
section 12 of Mozilla CA Certificate Inclusion Policy v2.
9 matches
Mail list logo