|
@vathpela | |||||
|
TFW you discover all EFI firmware is accidentally only able to express UT1 time, not UTC, and all of our system clocks are off by 37 seconds.
|
||||||
|
||||||
|
Paul Moore
@securepaul
|
30. sij |
|
For now, we'll have another leap second before too long and then everything will be off by either 37 *or* 38 seconds for a brief period of time. Fun!
|
||
|
|
||
|
Farce Majeure🌹
@vathpela
|
30. sij |
|
Yeah, exactly. Also there are some very specific times where timestamp-based Secure Boot blacklisting won't work right, and that's without even touching any actual clock hardware.
|
||
|
|
||
|
Steven Lucy
@slucy
|
31. sij |
|
Was recently looking at JavaScript code for a transit tracking website and couldn’t figure out why it was adjusting all the times by 37s (hard coded!)
|
||
|
|
||
|
Farce Majeure🌹
@vathpela
|
31. sij |
|
Probably only tangentially related; most system clocks are set through the OS, so only the firmware will show the time wrong, and even if you set it in the firmware the first time NTP will fix it.
|
||
|
|
||
|
Julia Kreger
@ashinclouds
|
30. sij |
|
|
||