Fingerprints couldn't get stolen. Not in the way you mean in terms of breaking any security. Not any more/less than someone lifting your fingerprints off a glass with tape and making silicon tips with them. It's highly convoluted any way you look at it to jeopardize the enclave by tampering with the fingerprint sensor.
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.
Apple Releases Updated Version of iOS 9.2.1 to Fix Devices Bricked by 'Error 53'
- Thread starter MacRumors
- Start date
- Sort by reaction score
Fingerprints couldn't get stolen. Not in the way you mean in terms of breaking any security. Not any more/less than someone lifting your fingerprints off a glass with tape and making silicon tips with them. It's highly convoluted any way you look at it to jeopardize the enclave by tampering with the fingerprint sensor.
so just making sure i understand this, apple wrote the iOS so that it would lock the phone if it detected 3rd party hardware and because people complained they rewrote the iOS so it would work around the 3rd party hardware but they can't rewrite the iOS so FBI can get into an iphone to see who else is trying to kill americans....
my guess is that if someone had come into apple HQ and shot it up, apple would be the first ones to offer to unlock the phone.
priorities...
#americanlivesmatter
my guess is that if someone had come into apple HQ and shot it up, apple would be the first ones to offer to unlock the phone.
priorities...
#americanlivesmatter
So why are you still here talking about an "utter joke of a company"?
Maybe it's just me, but I'll never understand the appeal of frequenting a forum just to nitpick about every little thing a company does. Then again, it appears that blind haters love blind followers.
The funny part is that Apple actually waited until it's all over the tech news and lawsuit had been filed. Obviously the primary reason for this is them trying to nickel-and-dime every customers. I used to remember when Apple Care is actually covers in fixing your device without paying extra. Now they actually charge you calling it subsidized and pay more if you didn't enroll. Yes it does covers accidental damage but that was their excuse to start charging premium. Their popularity hurts most of us who used to enjoy a top notch customer service. I used to hear a lot of stories that Apple fixes even accidental damage for free, my friend is one of them. That's how I started buying their product although the price is way higher than competition but the service is awesome. Basically the price I'm paying for the product back then is justifiable. Although their product still good but the price we're paying is because of popularity. The service still better than other competitors but it comes with a price. They surely made their investors really happy.
I seem to be an android user hahahaha stereotyping much? And for your hysterical tin foil hat attitude here is the facts in what the FBI DID ask Apple for:
http://www.bbc.co.uk/news/technology-35601035
The FBI wants Apple to alter what is known as a SIF - System Information File. In this context, the FBI is basically referring to the software that runs on the device. The FBI wants Apple to create a new SIF to place on Farook's iPhone that will allow it to carry out several functions normal iPhones do not allow.
The FBI wants to be able to:
- Prevent the phone from erasing itself. If certain security settings are enabled, after 10 failed attempts at entering a passcode, an iPhone can erase the personal data on the device. The FBI doesn't want to this to happen on Farook's phone.
- Automate the process for trying out passcode combinations. Farook used a four-digit passcode, for which there are 10,000 possible combinations. The FBI doesn't want to have to guess them all manually, and so it wants Apple to allow the passcode to be tried electronically. This means the FBI could simply instruct a computer to try every passcode, something that would take just minutes, possibly seconds...
- …and without unnecessary delay. The iPhone prevents you from entering a passcode for longer and longer periods of time each time you get it wrong. The FBI wants this barrier removed.
- Control the process, but not know how it's done. This is an interesting line, as it is suggests the FBI is willing to allow Apple to work on the phone at its own HQ, and in a way that doesn't risk the encryption software being released into the world.
So yeah, I WAS right. Perhaps you should change your news sources. And FYI I have an iPhone 6S, not that it's any of your business. Are you an Apple apologist that will do literally anything they ask? If we are stereotyping and all.
Yeah, you said it was a coding mistake, I said it was a move to force you to pay Apple more money to have your phone fixed, funny how Apple officially stated something completely different to both of us last week:
“We protect fingerprint data using a secure enclave, which is uniquely paired to the touch ID sensor. When iPhone is serviced by an authorised Apple service provider or Apple retail store for changes that affect the touch ID sensor, the pairing is re-validated. This check ensures the device and the iOS features related to touch ID remain secure. Without this unique pairing, a malicious touch ID sensor could be substituted, thereby gaining access to the secure enclave. When iOS detects that the pairing fails, touch ID, including Apple Pay, is disabled so the device remains secure.”
She adds: “When an iPhone is serviced by an unauthorized repair provider, faulty screens or other invalid components that affect the touch ID sensor could cause the check to fail if the pairing cannot be validated. With a subsequent update or restore, additional security checks result in an ‘error 53’ being displayed … If a customer encounters an unrecoverable error 53, we recommend contacting Apple support.”
https://www.macrumors.com/2016/02/05/error-53-home-button-iphone-brick/
This story today should have the picture of a reversing dump truck in the title with the beeping sound playing on a constant loop. It's pure unadulterated Apple damage control and severe reversing all in one, I bet a million the lawyers looked into it, realised they had actually breached it, and hence this humongous reversing on their stance.
I love people like you, so so so quick to judge and sentence with no actual insight into why people are here or what Apple products they own. Perhaps you should look into that, do you look at people in everyday life and make automatic assumptions and judgements about them? Without ever speaking to them?
I for instance never personally understand blind followers that get sucked in by everything Apple say's, spins, backtracks on apologizing for them all the way, I truly believe if Apple told some people to stick their fingers into the fire they actually would.
Last edited:
Actually, between Hanlon's razor and Occam's razor, it seems that it all simply being essentially a bug makes more or at the very least just as much sense.
[doublepost=1455836051][/doublepost]
Comparing a factory check that was enabled in an iOS update and that was simply then removed/disabled in a patched update to essentially just bypassing built-in encryption...not really even an apples to oranges comparison, let alone an apples to apples one.
Last edited:
Didn't apple stores tell people the only thing they can do is sell them a new iPhone?
It would have been more honest to say "wait for an update".
If anyone actually did buy a new iPhone because of this they should ask apple for their money back.
It would have been more honest to say "wait for an update".
If anyone actually did buy a new iPhone because of this they should ask apple for their money back.
Yes, that is exactly what they said, hand over several hundred of your currency for a new phone and you have lost all your phones data, though.
I make no judgments beyond what I observe, and I generally give people the benefit of the doubt. For example, nothing I've ever seen you post on this website would cause me to believe that you are anything less than a good person. I have no reason to negatively judge your character, so I won't. On the other hand, I don't need to know what Apple products you own to see that the vast majority of the posts that I've seen from you either discredit something that Apple has done, or vehemently disagree with someone about said thing that Apple has done. Which is no sin at all, of course, but it leads me to believe that you are inherently biased against Apple.
But like I alluded to earlier, I'm not trying to demean your character... it's the internet, people bicker. I'm sure you can nail me on some things I've said and done in the past, and I'll accept that. I just legitimately can't see myself ever talking too much about a company I don't like... I'm content to just go cold turkey on their products and walk the other way. Different strokes for different folks, I suppose.
And how many hundreds of dollars do we have to hand over for this update? Exactly zero!
Well, it was originally reported as people seeing the error after getting 3rd party Touch IDs, and Apple didn't budge on that.
Last edited:
Seems like Apple's reply that is mentioned in the article that this thread is about addresses that part of it.
...and as I predicted you cannot offer up a rational, logical argument why you should be able to break your iPhone and have Apple pay for it. To quote a phrase that seems to be all the rage around here : duh.
That's the apple i like
Which part?
Apple having a bug that bricks phones or Apple lying about why the bricking happened?
It would be pretty bad if apple stores are continuing to say to people that all they can do is sell them a new iPhone - in the hope they haven't read today's tech news sites and are therefore blissfully unaware of the existence of this update. If apple store staff didn't know such an update was coming maybe they still don't know. In any case clearly there needs to be better communication from Apple headquarters with apple store staff.
Seems like Apple, like pretty much any company, would disseminate information internally either before or at least at the same time as they would publicly.
Probably not without a few people handing over several hundred of their currency due to Apple's illegal money gouging exercise.
You very obviously haven't looked very far into my comments history then. Like most, you seem to have only ever read the negative ones and seem to magically, or never read the threads with the positive ones. It is making judgments based on closed limited views and opinions whether you realise it or not.
I am someone who is capable of hating things a corporation does and liking things it does, I do not and never ever will adhere to this 'must support all or nothing' attitude people seem to think you must have to be a fan of Apple? That's a mindset that is totally sucked in by Apples marketing spin machine, the perfect consumer that Apple loves.
What you're doing there... yeah, that's called conflation. It works if you don't think about it too critically. If you believe their latest explanation, they simply removed testing code in an update. Code that shouldn't have been there in the first place. iOS will still lock Touch ID functionality, just like it always did. It just won't lock the other functionality any more because, according to Apple, it never should have in the first place. Trying to tie that situation to the FBI situation requires one to forego logic and common sense.
Encryption is a separate issue deserving it's own discussion; not some mishmash of topics thrown together haphazardly like a potluck. That's what politicians do: conflate and deflect without ever actually making a relevant point.
Apple today released an updated version of iOS 9.2.1, which is designed to prevent the "error 53" device-bricking message that some iOS users received after having their iPhones or iPads repaired by third-party services using components not sourced from the original device.
Non-matching repair components that affected the Touch ID fingerprint sensor caused an iOS device to fail a Touch ID validation check because the mismatched parts were unable to properly sync. The validation check occurred during an iOS update or restore, and when failed, Apple disabled the iPhone, effectively "bricking" it in an effort to protect Touch ID and the related Secure Enclave that stores customer fingerprint information.
Apple originally explained that error 53 was intentional, implemented as a way to prevent the use of a malicious Touch ID sensor that could be used to gain access to the Secure Enclave, but customers with bricked devices were not happy with the explanation and Apple found itself facing a class-action lawsuit.
Today's update will restore iPhones and iPads that have been disabled due to "error 53" to full working condition and it will ensure that future iOS devices that have had similar repairs will not be fully disabled. Touch ID will not, however, be accessible until Apple-authorized repairs are made to a device affected by the issue.
Alongside the new version of iOS 9.2.1, Apple has also published a support document outlining how customers can resolve the "error 53" problem, and it has issued an apology, shared by TechCrunch. Apple now says the error 53 bricking issue was meant to be a factory test and was never intended to affect customers.The updated version of iOS 9.2.1 is available through iTunes and is not designed for customers who update their devices over the air. It can be downloaded on the iPhone 6, 6s, 6 Plus, 6s Plus, iPad mini 3, iPad mini 4, iPad Air 2, and iPad Pro.
Article Link: Apple Releases Updated Version of iOS 9.2.1 to Fix Devices Bricked by 'Error 53'
Not the iPhone 5s? Wasn't the original person who reported on this an iPhone 5s user?
Yeah. Apple's new webpage says "Customers who paid for an out-of-warranty replacement of their device based on this issue should contact AppleCare about a reimbursement".
But my point is that they shouldn't have been telling people they need a new iPhone at the same time they were working on a free update that would fix the problem.