-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Made the screenlock authenticator try to use StrongBox and attestatio…
…n if available, by try again without them if it doesn't work
- Loading branch information
1 parent
667ac95
commit 8e0aa42
Showing
1 changed file
with
41 additions
and
2 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
8e0aa42
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should allow easier use of Passkeys? As in microG actually managing the keys themselves.
If microG starts to be trusted for FIDO2 Keys, it should definitely attempt to use Strongbox, failing that a TEE.
Does this logging come up to the UI?
8e0aa42
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We currently don't fully support passkeys, as we don't have support for discoverable credentials. Adding discoverable credentials will need some more thoughts on UI, Backup and Sync (as it makes microG effectively a password manager). Once we have it, we definitely will show information about the security of that password manager (Strongbox or TEE, w/ or w/o attestation) in the corresponding UI.
8e0aa42
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah that's fair enough, cheers