Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upGitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
[Documentation] Fingerprint lock and encryption #590
Comments
gpa
changed the title
|
The encryption key is persisted to the protected storage area on the device (keychain or key store). |
|
In my opinion, on reboot all instances (app and auto fill extension) should be locked. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.