Post ApiQJUbPchjddOSoTo by nil@furry.engineer
(DIR) More posts by nil@furry.engineer
(DIR) Post #ApeOCZgvKMr8qjm8lk by nil@furry.engineer
2025-01-01T20:47:47Z
10 likes, 14 repeats
me neither, solaris
(DIR) Post #ApeOCh9tZ3Bq0cNsOm by nil@furry.engineer
2025-01-01T20:48:48Z
2 likes, 0 repeats
i spent hours trying to get this program to run for the bit and then gave up and just faked it with a shell script. why am i like this :)
(DIR) Post #Aphojgv8eP2Z6qkvom by divVerent@blob.cat
2025-01-03T13:01:00.776207Z
0 likes, 0 repeats
@nil Protip: set the year to 1997, which has the same week days and leap year rules as 2025. ;)
(DIR) Post #ApiQJUbPchjddOSoTo by nil@furry.engineer
2025-01-01T21:41:26Z
0 likes, 0 repeats
ok now i'm curious. i'm opening up the program in ghidra, and it turns out there's a check for the future and the past?? and there's debug symbols too, so that's nice... i'll try to clean up the decompilation of validate_system_time and show what it does
(DIR) Post #ApiQJVoD8bZDNNSY4G by nil@furry.engineer
2025-01-01T22:22:10Z
0 likes, 0 repeats
the majority of this function is just parsing a hardcoded string ("Mar 1 2004") to convert it to year, month, and date integers. this isn't the future limit date, btw. the program also checks if the date is too far in the *past*. looks like the hardcoded last allowed time you can run this program is midnight on December 31, 2009
(DIR) Post #ApiQJWhrng5Q9zUzom by nil@furry.engineer
2025-01-01T22:51:22Z
2 likes, 0 repeats
so if it makes anyone feel better i just got the actual real code to print out the message. i had to nop out everything before the time validation function so it would run (the sunpci hardware isn't emulated on qemu), but indeed this program does check the date and exit if it's too far in the future