Whose Clock Are You Patching On?
This week a PHP patch shipped a day early because the embargo leaked, kernel bug reports landed on public mailing lists before anyone had a fix, a GitLab flaw rated 10.0 turned out to reach back to a version from 2014, and a certificate authority announced it is leaving the TLS business while Chrome prepares to stop trusting one of its roots on Tuesday. Different stories, different vendors, one pattern: none of these dates were set by the people who have to act on them. Whose clock are you...
.png?width=1153&height=768&name=Untitled%20design%20(7).png)
.png?width=1153&height=769&name=Untitled%20design%20(9).png)
