wiggin

About

Username
wiggin
Joined
Visits
32
Last Active
Roles
member
Points
258
Badges
0
Posts
2,265

Reactions

246Like0Dislike12Informative

  • Lawfirm considers suit over iPhone's Touch ID-connected 'Error 53'

    wigginwiggin
    ericthehalfbee said:
    Why do people still (incorrectly) say this is a "new" problem with iOS 9? It's not, and has been around since at least iOS 8 (and possibly sooner, though I didn't see any in a quick search).

    https://discussions.apple.com/thread/7121903?start=0&tstart=0

    This guy went from iOS 8.3 to 8.4 and it happened. Another Apple Support thread has someone with it on 8.2. So clearly this is not new or unique to the latest version of iOS 9.

    As to why it only occurs when updating, a little common sense/logic needs applying. When you repair an iPhone you obviously turn it off. When turned back on, it "knows" the Touch ID sensor is different. At this point is when your authorized repair person would connect your iPhone to their system and perform the pairing procedure.

    If your iPhone bricked immediately upon power up, how could you ever properly repair (and then pair) Touch ID. When you do an update to a newer iOS version is when it bricks. At this point Apple realizes this was an unauthorized repair and no technician is going to do any pairing. The ONLY thing I think Apple could do different is put a warning after power up notifying the user and telling them their iPhone will be disabled after X amount of time. Then the customer would know at the time of repair what happened. 
    Yes, a little common sense... because at this point if your phone is in the hands of the bad guys who figured out a way to circumvent Touch ID it utterly too late anyway. The bad guys aren't ever going to install any updates (this is the common sense part) so the bricking is a completely useless action as it only affects the legitimate owner of the phone.
    muppetrycurt12

  • Lawfirm considers suit over iPhone's Touch ID-connected 'Error 53'

    wigginwiggin
    SpamSandwich said:
    steviet02 said:
    Nonsense! Replacing the Touch-ID with HW that is appropriate should just clear all the secure information in the ID chip and erase all Apple Pay information, not render the phone useless. The user then has to start over entering fingerprints and CC information, assuming they know the iCloud account that was tied to the phone. Why is that such a big deal for Apple to deal with?
    If the Touch ID enclave has been compromised AT ALL the phone needs to be bricked.
    Maybe. But, if this is such a critical security issue why does the check only take place when the OS is updated? Why wouldn't the check take place every time the phone is booted? Oh yeah, if someone steals my phone and tampers with the Touch ID system, before they try to read all of my data they are going to first let the phone contact Apple's servers, download, and install the latest updates.

    Utter nonsense. Certainly the Touch ID system has to be deactivated. You could even argue that the phone get locked with only Apple being able to unlock it. But to think that permanently bricking the phone is the right solution is crazy. And no, I don't really think this was an intentional ploy by Apple to force users to only use authorized repair services (to the envy of car dealers across the US). It's probably a small enough revenue stream to not really care about. More likely it's just arrogance and/or short-sightedness to not fully think through the consequences of their system designs.
    curt12