News for hackers. Stuff that matters.
Re:Securing a travel iPhone by mahyarm on Friday July 08, 2016 @10:00PM (#12059731)
If you expect you can reliably turn off your phone (7 seconds) before you get in a search situation, then use a full password instead of a numeric pin, then touch ID is a great balance of convenience and security. TouchID also prevents shoulder surfing of your code.

It's all about the threat model.

Re:Securing a travel iPhone by watson on Saturday July 09, 2016 @04:30AM (#12060672)
Correct me if I'm wrong, but isn't it also possible to just use one of your fingers that you didn't register with touch ID for 5 or so consecutive unlock attempts and it will have the same effect as rebooting your phone?
Re:Securing a travel iPhone by notjosh on Saturday July 09, 2016 @06:50AM (#12060911)
There is a slight difference.

Keychain and NSFileManager have possible modes of "kSecAttrAccessibleAfterFirstUnlock" [0] and "NSFileProtectionCompleteUntilFirstUserAuthentication" [1] respectively that are (fittingly) in an open state within your app after you've unlocked the device.

[0]: https://developer.apple.com/reference/security/ksecattracces...

[1]: https://developer.apple.com/reference/foundation/nsfilemanag...

Re:Securing a travel iPhone by TazeTSchnitzel on Sunday July 10, 2016 @01:59PM (#12066459)
That will stop you using Touch ID thereafter, but it's quite slow to do in practice.

As an aside, I've found that, at least with my iPhone 5S, if my finger is wet (e.g. if I've licked it), it also is rejected.