Am I just overthinking this?
I like Keepass2Android because of it’s “QuickUnlock” feature, but it looks very old, is mainly distributed via Google Play and not on the official Fdroid repo. (Also, doesn’t google now have the signing keys of all apps now? Kinda sus if Google could just sign updates and bypass the developers)
KeepassDX seems more secure, since the Fdroid and Google Play versions are separate, using (I assume) separate signing keys, so Google cant sign an update for the Fdroid version. Looks more “Modern” but it lacks the “Quick Unlock” feature, so biometrics is the only convient way to quickly unlock it, I prefer something like “Quick Unlock” feels more secure (since theres no shenanigans like replicating a fingerprint to fool the biometrics scanner).
TLDR: I really want the “QuickUnlock” feature of Keepass2Android, but with the Google policy of having the signing keys, I’m kinda sus.
Am I overthinking this?
I use KeepassDX. Love it. I really like biometric unlock on apps, but I don’t use it to unlock my phone.
I have been using keepassdx for years and am happy with it
It’s KeepassDX for me, works great. If there is an F-Droid alternative then that is what I use.
FYI The IzzyOnDroid repo still provides the Keepass2 Android Offline version.
Man, at this point you should think about your treat model. Are you a high profile target? If so, choose security over convenience, but if you only want your privacy, you probably can have a comfortable balance between security and convenience.
I use keepass2Android.
Man, at this point you should think about your treat model.
Terry finishes some paperwork and he gets a chocolate nib.
xD
I mean, the 2 options I’m thinking is:
Use KeepassDX (installed via Fdroid) + Biometrics
(downside being the possibility of Biometric exploits)
Or
Use Keepass2Android + Quick Unlock (without biometrics)
(downside being Google doing malicious update)
Which would be the “more secure” option?
(I don’t want to type the entire passphrase every time, that’s all I care about, but still want the most secure option that’s isn’t too inconvienient)
That’s what Arthur describes: you’re comparing from my point of view two non issues against each other.
If you don’t have the profile that either warrants:
- Google would risk business revenue by having to handle a mittm attack done by them or
- someone investing in an elaborate scheme to get a fingerprint copy
And that being worth it instead of just getting you personally is a very specific threat model where I lack the fantasy on what would warrant that.
Or to give the relevant xkcd:
And to answer your specific question: I personally went with keepass2android and have neither issues nor concerns so far.
Another issue with Google Play is that there’s nothing stopping the developer from pushing out an update that doesn’t match the published source. It isn’t tied to GitHub or anything.
Developers with apps on Google Play are frequently targeted with buyout requests from scammers looking to get malware to an existing user base. Or even if it’s not explicitly malware, it could be closed-source.
For example, the “Simple Mobile Tools” app developer sold their apps a year or two ago. Now they have ads, in-app purchases, and god knows what else. If you had installed them from Google Play, you would have received these updates automatically. Those new versions don’t exist on f-droid, naturally. Anyone who was using them should really uninstall them and install the “Fossify” forks from f-droid.
Every developer ID publishing on Google Play is potentially for sale. There are no real safeguards against this, and you might never know. At least with F-Droid it’s verified as open source and malicious (or just plain crappy) updates can be identified and dealt with, either by f-droid maintainers or by end users.
Oh yeah I agree with that and s good point! Google Play Store is convenient but… Well I circumvent it where possible, more due to the tracking mania but your points added to my sensitivity,so thank you!
Both are fine, take the easiest.
i quite like authpass
You can also install K2A directly from github through obtainium or manually.
