github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-05-07 11:29:37 -05:00
Code Issues 1.1k Packages Projects Releases 122 Wiki Activity

[GH-ISSUE #590] [Documentation] Fingerprint lock and encryption #6843

New Issue
Closed
opened 2026-04-10 23:11:43 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-04-10 23:11:43 -05:00
Owner
Copy Link

Originally created by @gpa on GitHub (Sep 2, 2019).
Original GitHub issue: https://github.com/bitwarden/android/issues/590

I logged in with my passphrase to the mobile app and then set the fingerprint lock. I just assumed that the unencrypted data is kept in memory and then only shown after a fingerprint verification. But then I restarted my phone and was still able to access the data with just the fingerprint. From reading the source code I could see that a FingerprintUnlockKey is being used, but it is unclear to me how it works and would really appreciate some documentation on it and how it compares to just using the password security-wise.

Originally created by @gpa on GitHub (Sep 2, 2019). Original GitHub issue: https://github.com/bitwarden/android/issues/590 I logged in with my passphrase to the mobile app and then set the fingerprint lock. I just assumed that the unencrypted data is kept in memory and then only shown after a fingerprint verification. But then I restarted my phone and was still able to access the data with just the fingerprint. From reading the source code I could see that a FingerprintUnlockKey is being used, but it is unclear to me how it works and would really appreciate some documentation on it and how it compares to just using the password security-wise.
GiteaMirror commented 2026-04-10 23:11:44 -05:00
Author
Owner
Copy Link

@kspearrin commented on GitHub (Sep 2, 2019):

The encryption key is persisted to the protected storage area on the device (keychain or key store).

<!-- gh-comment-id:527149867 --> @kspearrin commented on GitHub (Sep 2, 2019): The encryption key is persisted to the protected storage area on the device (keychain or key store).
GiteaMirror commented 2026-04-10 23:11:44 -05:00
Author
Owner
Copy Link

@uchagani commented on GitHub (Oct 2, 2019):

In my opinion, on reboot all instances (app and auto fill extension) should be locked.

<!-- gh-comment-id:537333532 --> @uchagani commented on GitHub (Oct 2, 2019): In my opinion, on reboot all instances (app and auto fill extension) should be locked.
GiteaMirror commented 2026-04-10 23:11:45 -05:00
Author
Owner
Copy Link

@vvolkgang commented on GitHub (Jun 20, 2024):

Issue migrated to https://github.com/bitwarden/mobile/issues/590

<!-- gh-comment-id:2181551472 --> @vvolkgang commented on GitHub (Jun 20, 2024): Issue migrated to https://github.com/bitwarden/mobile/issues/590
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
app:authenticator
app:password-manager
bug
bug-passkey
customer-support
duplicate
enhancement
good first issue
help wanted
needs-reply
needs-response
pull-request
Mirrored from GitHub Pull Request
 question
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#6843
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?