3 ms·
Interestingly, over at the Google Certificate Transparency group, it looks like both StartCom's and WoSign's CT log servers were recently included into Chrome.
by 0x0 10y ago
Interestingly, over at the Google Certificate Transparency group, it looks like both StartCom's and WoSign's CT log servers were recently included into Chrome.
https://groups.google.com/a/chromium.org/forum/#!topic/ct-policy/4BNen-sogf8 https://groups.google.com/a/chromium.org/forum/#!topic/ct-po...
- iancarroll 10y agoLuckily CT logs are designed to be mostly trustless.
- 0x0 10y agoYet the Izenpe CT log managed to be untrustworthy enough to be de-listed! https://groups.google.com/a/chromium.org/forum/#!topic/ct-policy/g0WWgUodpOk https://groups.google.com/a/chromium.org/forum/#!topic/ct-po...
- iancarroll 10y agoIndeed. For those curious, CT is designed to "discover" SCTs that were not publicly shown by the log, so that the log can operate without a lot of trust, though this did not happen here (someone just found them operating two logs...) I guess I'm not the best person to criticize other logs, though. :-)
- dorianm 10y ago"Please note that while both Symantec and CNNIC's logs are presently enabled in the current Chrome stable release (Chrome 52), both WoSign and StartCom's logs will not be recognized until Chrome 54, which is presently the Dev channel release."
- randomfool 10y agohttps://googlechromereleases.blogspot.com/2016/10/stable-channel-update-for-desktop_20.html https://googlechromereleases.blogspot.com/2016/10/stable-cha... Chrome 54 is now in stable.