On 11/11/15 14:02, B.R. wrote:
It is sad Chrome kind of forces website owners to have Certificate
Transparency available while the whole things is still categorized as
'Experimental' by the IETF to this day:
https://tools.ietf.org/html/rfc6962
... but that is another debate. If you w
It is sad Chrome kind of forces website owners to have Certificate
Transparency available while the whole things is still categorized as
'Experimental' by the IETF to this day:
https://tools.ietf.org/html/rfc6962
... but that is another debate. If you wanna serve CT certificates fro
On 11/11/15 11:03, locojohn wrote:
Joó Ádám Wrote:
---
The TLS extension is the only method to implement Certificate
Transparency without the assistance of the CA, and starting with
January 1 2015 Chrome refuses to display the green bar for
Joó Ádám Wrote:
---
> The TLS extension is the only method to implement Certificate
> Transparency without the assistance of the CA, and starting with
> January 1 2015 Chrome refuses to display the green bar for EV
> certific
Hi Maxim,
> Given that's all about EV
> certs, switching to a different CA is a solution to consider if a
> particular CA doesn't support CT.
My understanding is that it is something that would benefit the entire
ecosystem, not just EV sites, but I understand if this has no
priority. I guess CAs
ginx-ct)
No plans.
> The TLS extension is the only method to implement Certificate
> Transparency without the assistance of the CA, and starting with
> January 1 2015 Chrome refuses to display the green bar for EV
> certificates without Certificate Transparency.
>
> StartSSL is
Transparency without the assistance of the CA, and starting with
January 1 2015 Chrome refuses to display the green bar for EV
certificates without Certificate Transparency.
StartSSL is one CA that currently does not support other methods,
which means a lot of sites suffers from this.
Á
