Already in Chrome stable?
-
-
-
I’ve coded Hardenize to show errors if TLS connections with new certs are not CT compliant, but am I right? And where do I point people as an explanation? :)
1 reply 0 retweets 2 likes -
Replying to @ivanristic @sleevi_
I am not on Chrome but I would point athttps://groups.google.com/a/chromium.org/forum/#!topic/ct-policy/wHILiYf31DE …
2 replies 0 retweets 0 likes -
From that doc: "Chrome will start enforcing that all TLS certificates issued after April 2018 comply with the Chromium CT Policy [5] in order to be trusted."
1 reply 0 retweets 0 likes -
Yeah, but it doesn’t exactly say when they will begin to enforce, just that certs after April are affected.
2 replies 0 retweets 0 likes -
A-ha! So it would probably be more appropriate to use warnings rather than errors in Hardenize in the initial weeks (if non-compliance is detected)?
0 replies 0 retweets 0 likes
I do wish Chrome shipped enforcement prior to deadlines, to avoid misunderstandings like this and the risk of a Chrome upgrade being seen as the cause of breakage :-)
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.