Do you mean unsecured networks? Because I don't think any devices connect to random unknown networks.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
New Version of 'January 1, 1970 Bug' Can Brick Pre-iOS 9.3.1 Devices Over Compromised Wi-Fi Networks
- Thread starter MacRumors
- Start date
- Sort by reaction score
No. The bug was fixed, but unpatched systems can apparently have the bug triggered via a rogue NTP server on a wi-fi network with a 'trusted' name. That was the new discovery.
Actually I've just reread the article and I made the same mistake as you. They did goof between iOS 9.3 and 9.3.1...
Yeah. Clocks/calendars are one of those things that are deceptive. On the surface, they seem simple, because we (as humans) deal with them in both large enough chunks (fairly large fractions of a second), and small enough chunks (a few years) at any point in time, that most of the idiosyncrasies can be glossed over. For example, unless you hear about it in the news, you'll never notice the leap-seconds that get added periodically.
On the other hand, computers work in units of time small enough that errors can accumulate rather rapidly, *and* have to handle spans of time long enough that you're talking *centuries*, minimum.
For example:
Everybody knows that there's a leap year every 4 years.
*Some* people know that there is no leap year every 100 years.
*Few* people know that there is still a leap year every 400 years.
Virtually nobody knows the further set of exceptions beyond that, and that's just one example of calendar-level rules that you have to take into account when dealing with time.
[doublepost=1460580275][/doublepost]
That's actually only an issue in 32-bit Unix flavors. (Or possibly some weird 64-bit flavors that for some reason kept time_t defined as a 32-bit integer.)
Throw in time zones, daylight saving, and all that "fun".
[doublepost=1460580574][/doublepost]
https://forums.macrumors.com/threads/the-iphone-apocalypse-january-19-2038.1943912/
I think I conflated the "Ask to join networks switch" with the text below it that talks about joining known networks automatically. I've had that switch turned off for years. But yes, also unsecure networks I try to avoid. I'm just wondering with this switch off, if it will connect to other networks with the same name as trusted ones? That's what I'm not sure about.
Sure it would if the password and encryption are the same. Or unsecured networks with default names like "linksys" it would connect anytime it was near "linksys". There was an Apple KB regarding that stating to not use default wifi names on your routers. (some preferred setup KB I think it was)
[Edit] here is the Apple KB
I can do the OTA or even apply the update on my Mac Pro 1,1 running iTunes in Lion, but after my phone reboots and would not longer show up in iTunes to sync apps, music, photos, calendar, ringtones.
Why would I want to break my computer/phone syncing. Nope.
So you can cook steak with an iPad now!?
That's so cool, and handy if your stuck out somewhere...
That's so cool, and handy if your stuck out somewhere...
Yeah, leap-stuff, time zones, daylight savings time, and fractional seconds become a nightmare.
Well, a random unknown network could have the same name as a known one, and then you'll auto-join it.
Yes Apple should resolve this, but realistically speaking of the millions of iPhone owners, who is actually going to experience this in real life in their day to day use?
Well the rest of the industry manages with them just fine. Hell, my Windows 95 laptop was bad at a lot of things, but it could tell the time and date with no issues.
Just as iOS could, just a few issues with some less than typical cases. Not to mention thst Windows has been getting patches and updates for all kinds of things (including time and date related ones) on a fairly regular and frequent basis for years and years. Similar things go for the rest of the industry.
Seems like it's just a story with more information about the same thing, which Apple has already addressed, and not really something new.
Dear Apple, if you're reading this, I have come up with a solution, and I've made it open-source as of this message.
I'm no programmer, but how about running this piece of code whenever the date is changed either manually or automatically:
The thing I've noticed about time is that it usually doesn't tend to go backwards. So once it's 2016, you can be pretty certain that the year will never go back to anything less than that, at least not for a very long time.
You're welcome, and yes I'm available for work. I specialize in simple if/then statements, and time travel, if you're wondering.
I'm no programmer, but how about running this piece of code whenever the date is changed either manually or automatically:
Code:
If (currentYear < 2016){
currentYear = 2016
}The thing I've noticed about time is that it usually doesn't tend to go backwards. So once it's 2016, you can be pretty certain that the year will never go back to anything less than that, at least not for a very long time.
You're welcome, and yes I'm available for work. I specialize in simple if/then statements, and time travel, if you're wondering.