News for hackers. Stuff that matters.
Re:Face ID and Touch ID for the Web by thephyber on Wednesday June 24, 2020 @03:13PM (#23632513)
From the server side, isn't this just a WebAuth integration?

How does the server know for sure if the client is on an iOS Safari browser on an iPhone with FaceID or a custom browser on any OS and any non-locked-down hardware being run with Selenium?

Re:Face ID and Touch ID for the Web by blintz on Wednesday June 24, 2020 @03:21PM (#23632621)
Attestation. If a website requests it, the device will provide cryptographic proof that you used a specific vendor’s device to store the resident credential. The proof is a certificate signed with a vendor’s secret attestation key.
Re:Face ID and Touch ID for the Web by Siira on Wednesday June 24, 2020 @03:27PM (#23632707)
Can't the key get stolen if it's on the client?
Re:Face ID and Touch ID for the Web by amluto on Wednesday June 24, 2020 @03:30PM (#23632749)
Yes, but it’s probably stored in the Secure Enclave, so it’ll be hard work.
Re:Face ID and Touch ID for the Web by bfulgham on Wednesday June 24, 2020 @06:51PM (#23634758)
Correct. The key material is stored in the Secure Enclave.
Re:Face ID and Touch ID for the Web by jacobr1 on Wednesday June 24, 2020 @03:47PM (#23632987)
The question is more along the lines of: does this provide more security than passwords for real users?

Stealing a password is probably more easily done than stealing a private key that is never transmitted. The primary threat model is protecting the credentials of real users rather than protecting against fraudulent users (though some considerations have been made for that too).

Re:Face ID and Touch ID for the Web by thephyber on Wednesday June 24, 2020 @04:29PM (#23633464)
While what you say is true, it doesn't seem relevant to this thread.