You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Additional encryption by a device-bound key stored in the Secure Enclave
It would be useful to compliment the app logic with keychain-based verification, where the system itself would verify user-defined access conditions.
For example, the user could configure the app to require a biometric scan (or PIN code) to open the database. Instead of doing the check in the code, the app should set the corresponding attribute on the keychain item. This way, access control would be enforced by the system rather than the app.
Currently, sensitive data in the keychain is protected by three factors:
kSecAttrAccessibleWhenUnlockedThisDeviceOnly
attributeIt would be useful to compliment the app logic with keychain-based verification, where the system itself would verify user-defined access conditions.
For example, the user could configure the app to require a biometric scan (or PIN code) to open the database. Instead of doing the check in the code, the app should set the corresponding attribute on the keychain item. This way, access control would be enforced by the system rather than the app.
This would be a prerequisite for #42 and #169.
[thanks, Konstantin and Andy]
The text was updated successfully, but these errors were encountered: