Re:Out of date Chrome results in ERR_CERTIFICATE_TRANSPARENC...
by wnevets on Monday December 12, 2016 @02:55PM
(#13161331)
am I the only one who had trouble reading that title?
[ Parent
| on HN ]
Re:Out of date Chrome results in ERR_CERTIFICATE_TRANSPARENC...
by fail2certError on Monday December 12, 2016 @03:03PM
(#13161408)
You are not the only one.
Skimming the ticket comments, it smells like an idea that, ten weeks after Google's compile, a given release will start throwing SSL cert handshake alarms for at least some major websites.
Anybody that does not permit Chrome to auto-update might anticipate many intrusive SSL security warnings, every 10 weeks or less.
While you may have downloaded and installed Chrome on a given date, the download's compilation timestamp could be any point up to ten weeks in the past?
All because anti-virus?
Re:Out of date Chrome results in ERR_CERTIFICATE_TRANSPARENC...
by __jal on Monday December 12, 2016 @03:19PM
(#13161535)
Not anti-virus. Symantec. You might even call it a bit pro-Symantec, in that the time bomb is an accommodation added especially for them. I certainly would not call it antisymantec.
Re:Out of date Chrome results in ERR_CERTIFICATE_TRANSPARENC...
by detaro on Monday December 12, 2016 @03:22PM
(#13161561)
A specific release had a bug that caused this, it's not planned behaviour and should not happen in the future.
Re:Out of date Chrome results in ERR_CERTIFICATE_TRANSPARENC...
by Retr0spectrum on Monday December 12, 2016 @03:10PM
(#13161471)
My brain seemed to skip over the strange part, so I just read it as "Chrome built-in time-bomb of 10 weeks". I didn't even notice until I read your comment.
Re:Out of date Chrome results in ERR_CERTIFICATE_TRANSPARENC...
by DuckyC on Monday December 12, 2016 @03:03PM
(#13161413)
it could also have been built-in build-time time-bomb.
Re:Out of date Chrome results in ERR_CERTIFICATE_TRANSPARENC...
by Retr0spectrum on Monday December 12, 2016 @03:12PM
(#13161483)
Built-in build-time time-bomb with 10 week timer.