News for hackers. Stuff that matters.
Re:iPhone Thief Explains How He Breaks into Your Phone [video] by cassianoleal on Thursday December 21, 2023 @09:08AM (#38720545)
Yeah this is pretty glaring.

Changing the biometrics should automatically invalidate all FaceID tokens and block falling back to device PIN. It should effectively log the device out of all services, perhaps even delete browser cookies etc. since it should mean the person holding the phone is not the one who logged on to those.

Of course, this could have other implications so a lot of care has to be taken when designing and implementing this.

Re:iPhone Thief Explains How He Breaks into Your Phone [video] by Tommstein on Thursday December 21, 2023 @11:33AM (#38722700)
Android appears to do something like this with fingerprints (or at least enable it). Whenever I add a new one, apps stop accepting fingerprints until I enter my password/passcode/whatever in each one.
Re:iPhone Thief Explains How He Breaks into Your Phone [video] by cassianoleal on Thursday December 21, 2023 @10:51PM (#38730755)
That's ok but in this case it won't help since the attacker already has the phone's passcode.
Re:iPhone Thief Explains How He Breaks into Your Phone [video] by Tommstein on Thursday December 21, 2023 @11:17PM (#38730882)
If each app has its own password/passcode that you can bypass with your fingerprint, and fingerprints suddenly stop working, it absolutely does shut down the thief, unless you also use the phone's passcode for all your accounts.
Re:iPhone Thief Explains How He Breaks into Your Phone [video] by cassianoleal on Friday December 22, 2023 @07:13PM (#38740303)
Oh I see. On the iPhone though, FaceID / TouchID are the same as the passcode - at least in the sense that if the biometrics fail, they fall back to the passcode.

This means that if you enable log in with biometrics, you’re essentially enabling the fallback along even if the app has a separate PIN/passcode.

Re:iPhone Thief Explains How He Breaks into Your Phone [video] by Shadowmist on Saturday December 23, 2023 @11:02PM (#38750996)
I just tried it on my iPhone with a banking app and it shows me the default login screen for the bank and then logs me in if my face is there, but without the face it just stays on the login screen waiting for me to enter the bank password, never asks for a PIN.
Re:iPhone Thief Explains How He Breaks into Your Phone [video] by cassianoleal on Sunday December 24, 2023 @08:29AM (#38753332)
Huh, I just tried this with a couple of my bank apps and they do the same. I guess either I'm misremembering this, or it got fixes along the way.

Wallet is still accessible with the device passcode as a fallback though, which means quite a lot of damage can still be done.

Re:iPhone Thief Explains How He Breaks into Your Phone [video] by pests on Sunday December 24, 2023 @12:10AM (#38751308)
The fallback is the service account password, not the local device PIN.
Re:iPhone Thief Explains How He Breaks into Your Phone [video] by snotrockets on Saturday December 23, 2023 @10:04PM (#38750715)
It does get invalidated if the app use the right api call: https://developer.apple.com/documentation/localauthenticatio...
Re:iPhone Thief Explains How He Breaks into Your Phone [video] by easton on Saturday December 23, 2023 @10:14PM (#38750758)
Microsoft’s apps use this (although, sometimes it gets triggered even if I didn’t change my biometrics).
Re:iPhone Thief Explains How He Breaks into Your Phone [video] by yunohn on Saturday December 23, 2023 @10:28PM (#38750821)
All banking and finance apps I use have this correctly setup.
Re:iPhone Thief Explains How He Breaks into Your Phone [video] by cassianoleal on Sunday December 24, 2023 @08:26AM (#38753315)
Therein lies the problem, I guess. How is it left to the application developer to implement this properly? As a user of the device, I expect biometrics (a feature of my platform of choice) to behave consistently.
Re:iPhone Thief Explains How He Breaks into Your Phone [video] by snotrockets on Sunday December 24, 2023 @09:01PM (#38758942)
Not all threats scenarios are the same. The problem is that there's very little in the way of forcing the app developers to accept liability if they misjudge the threat scenario (a notable exception are banking apps in the US)