4 ms·
am I the only one who had trouble reading that title?
by wnevets 10y ago
am I the only one who had trouble reading that title?
- pulse7 10y agobuilt-build-bomb
- fail2certError 10y agoYou 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?
- __jal 10y agoNot 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.
- detaro 10y agoA specific release had a bug that caused this, it's not planned behaviour and should not happen in the future.
- DuckyC 10y agoit could also have been built-in build-time time-bomb.
- Retr0spectrum 10y agoBuilt-in build-time time-bomb with 10 week timer.
- Retr0spectrum 10y agoMy 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.