3 ms·
Expired certificates should also at worst be a skippable warning. No one’s relying on certificates expiring for security. If you did you might have to wait many
by AnotherGoodName 1y ago
Expired certificates should also at worst be a skippable warning. No one’s relying on certificates expiring for security. If you did you might have to wait many years for the expiration of a stolen certificate - lol!
It’s absolutely a minor “hey btw the certificate expired, check for an update” yet various systems treat certificate expiration as an end of the world lock it down scenario.
- Tuna-Fish 1y agoOh it's skippable all right. Just pull the cmos battery and wait a few seconds before putting it back in.
- londons_explore 1y agoThere's gonna be a bunch of linux users who write a shutdown script to set the date back to 2015 then poweroff... And at startup, reset the date back to today using the internet. Sounds like a cleaner solution than any of the ones in the article too!
- Tuna-Fish 1y agoThat's risky, an unclean shutdown would require resetting the clock which is a bother. It's much more likely that someone will write a driver that adds an offset to the clock, keeping the hw date in a safe range.
- homebrewer 1y agoYou can simply avoid adjusting the hardware clock. The kernel clock is not tied to it and can be modified separately. chrony can do that, for example. https://wiki.archlinux.org/title/Chrony#Real-Time_Clock https://wiki.archlinux.org/title/Chrony#Real-Time_Clock
- andrewmcwatters 1y agoInfosec engineers hate this one trick!
- charcircuit 1y ago>years for the expiration of a stolen certificate Code signing certificates are trending down in length. Ot recently dropped down from a max of 39 months to about 15 months.