Conversation:

Notices

1. Bob Jonkman (bobjonkman)'s status on Sunday, 02-Jan-2022 23:11:09 EST Bob Jonkman

   Remote profile options...

   • LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864}
   From what I can tell, they were using the decimal digits of the 32-bit number as a sort of BCD, with the base10 digits representing portions of the date. The example used is "the new date value of 2,201,010,001 is over the max value of 'long' int32 being 2,147,483,647". So, YY MMDDHHMM ?
   
   What an extraordinarily stupid way to represent a date.
   • Alexandre Oliva (moved to @lxo@gnusocial.jp) (lxo)'s status on Tuesday, 04-Jan-2022 02:34:39 EST Alexandre Oliva (moved to @lxo@gnusocial.jp)

     Remote profile options...

     • Bob Jonkman
     what's most incredible about this date representation is that it was introduced after Y2K. it wouldn't have worked up to [19]99
     think about it. someone implemented that after all the many years of preparation and patching decades-old systems for Y2K, knowing (or, worse, without realizing) that it had at most a couple of decades of use. how screwy and irresponsible is that?
     Joshua Judson Rosen and Bob Jonkman like this.
     Bob Jonkman repeated this.
   • Bob Jonkman (bobjonkman)'s status on Tuesday, 04-Jan-2022 05:07:25 EST Bob Jonkman

     Remote profile options...

     • Alexandre Oliva (moved to @lxo@gnusocial.jp)
     According The Register's forum, this is the patch: "The current fix: Represent 2022-01-02 as 2021-12-33."
     
     https://forums.theregister.com/forum/all/2022/01/03/exchange_servery2k22_flaw/#c_4389861