News for hackers. Stuff that matters.

A comment on Changing Date to Jan 1, 1970 disables 64-bit iOS devices. Parent comment

Re:Changing Date to Jan 1, 1970 disables 64-bit iOS devices by mjmsmith on Saturday February 13, 2016 @05:23PM (#11095927)
Yep, this was my iPad after I had a broken screen replaced: http://blog.marksmith.org/too-much-security/

I had to reinstall from a backup to enable wifi so it could talk to an ntp server and sort itself out.

[ Parent | on HN ]
Re:Changing Date to Jan 1, 1970 disables 64-bit iOS devices by userbinator on Saturday February 13, 2016 @08:03PM (#11096571)
23510262 minutes from January 1st, 1970 is 2014 September 13, 01:42:00. Matches that date exactly.
[ Parent | on HN ]
Re:Changing Date to Jan 1, 1970 disables 64-bit iOS devices by obelisk_ on Sunday February 14, 2016 @04:20AM (#11097665)
Yes, they included that in their post below the picture.

    > NSDate dateWithTimeIntervalSince1970:23510262*60
    2014-09-13 13:42:00 +0000
Btw, are they using an Objective C repl?
[ Parent | on HN ]
Re:Changing Date to Jan 1, 1970 disables 64-bit iOS devices by jakobegger on Sunday February 14, 2016 @05:27AM (#11097782)
That might be fscript?

http://www.fscript.org

[ Parent | on HN ]
Re:Changing Date to Jan 1, 1970 disables 64-bit iOS devices by mjmsmith on Sunday February 14, 2016 @11:55AM (#11098946)
Yes, it's F-Script. Playgrounds pre-Swift :)
[ Parent | on HN ]
Re:Changing Date to Jan 1, 1970 disables 64-bit iOS devices by TazeTSchnitzel on Saturday February 13, 2016 @05:58PM (#11096105)
I'm surprised the default time/date is UNIX epoch + 0. Realistically, it ought to be the date that version of iOS was released.
[ Parent | on HN ]
Re:Changing Date to Jan 1, 1970 disables 64-bit iOS devices by natch on Saturday February 13, 2016 @06:22PM (#11096207)
No programmer ever wished for more special cases when integrating date handling code, especially on a networked device and one that's so tightly integrated with other platforms and devices. And imagine the nightmare of testing the device pre-release, all while faking out the dates, both local and on NTP servers and on development desktop machines the under-development devices are tethered to, and somehow knowing exactly when the release day was going to be, possibly years in advance. So... no, I'm not sure about that plan. And I guess the bug would be unaffected in any case.
[ Parent | on HN ]
Re:Changing Date to Jan 1, 1970 disables 64-bit iOS devices by TazeTSchnitzel on Sunday February 14, 2016 @11:26AM (#11098843)
> And imagine the nightmare of testing the device pre-release, all while faking out the dates

Huh? Why would you set the date to one in the future? Make the date be the one of the build.

[ Parent | on HN ]
Re:Changing Date to Jan 1, 1970 disables 64-bit iOS devices by rdancer on Saturday February 13, 2016 @07:32PM (#11096456)
Even if the implementation hurdles raised by others would be overcome, as I am certain they could be, this would help how?
[ Parent | on HN ]
Re:Changing Date to Jan 1, 1970 disables 64-bit iOS devices by ikeboy on Saturday February 13, 2016 @07:35PM (#11096472)
Presumably because it would be impossible to set the time back to 1970, avoiding associated issues.
[ Parent | on HN ]
Re:Changing Date to Jan 1, 1970 disables 64-bit iOS devices by rdancer on Sunday February 14, 2016 @12:28AM (#11097256)
... but it wouldn't prevent setting time to 2014. Again, how does this help?
[ Parent | on HN ]
Re:Changing Date to Jan 1, 1970 disables 64-bit iOS devices by cmrx64 on Saturday February 13, 2016 @06:25PM (#11096215)
Why is that realistic?
[ Parent | on HN ]