4 ms·
I'd claim that Microsoft pioneered this time limit security concept with Windows 95 almost 30 years ago. They went with 2^32-1 milliseconds or about 49.7 days.
by lysace 2y ago
I'd claim that Microsoft pioneered this time limit security concept with Windows 95 almost 30 years ago.
They went with 2^32-1 milliseconds or about 49.7 days.
We don't talk enough about Microsoft's strong legacy of security innovations, IMHO.
- yalok 2y agoI’m not sure it was because they cared about security - looks more like accounting for 32-bit timestamp rollover would be very disruptive to the huge (legacy) code base and it was a quick fix to work around the problem :)
- IshKebab 2y agoIt was a joke.
- Dwedit 2y agoTo this day, some programs malfunction after 2^31 milliseconds have passed since bootup, which is the halfway point. Milliseconds since bootup has just become negative, and has not rolled over yet. Just having a negative number of milliseconds is enough to mess with those programs.
- rvba 2y agoMore like "innovation" that makes all those machines in factories break every 49 days.
- philistine 2y agoI'm pretty sure you're joking. Windows 95 crashed if you sneezed in its general direction, I'm pretty sure it would blue screen due to some edge case well before 49 days of runtime.
- lysace 2y agoNo joke. https://web.archive.org/web/20041207171440/http://support.microsoft.com/kb/q216641/ https://web.archive.org/web/20041207171440/http://support.mi... https://web.archive.org/web/20130731171959/https://sites.google.com/site/edmarkovich2/whywindows95andwindows98wouldcrashafter49.7daysofuptime https://web.archive.org/web/20130731171959/https://sites.goo...