I will admit to new ~reuse~ on this from another class…
…but this is a different audience.
This may look like dry sysadmin stuff, and a very small paragraph mentioning the _kernel_timespec…but this is roughly the Unix version of Y2K where 32-bit systems have been counting seconds since January 1970…and time is running out.
Realistically (and for those of us who may be retired in 2038), setting a timeout into the future on a machine that is vulnerable in this way would cause a buffer overflow. I heard they are bad. And cause interesting, sometimes exploitable side effects…
…since I first read this any time a system of update has innocently offered me a date range ~20 years or so into the future~ I have weighed breaking something I like or need Vs. Rodger Rabbit suggesting it might be funny. Not a hard experiment for a VM…
https://www.linux.com/news/2018/8/linux-kernel-418-keeps-things-solid-and-secure
Hi Steve,
This is a very popular way to use time in system. It is also called as epcoh time. I used it in some of tools when i was working at my previous firm. When i brought up this point of the time would not work after 2038 the answer i got was its not a problem for us now and for future and we will look at it then. “Ignorance is bliss” is the approach the higher management was going with for now.