I refuse to use Google's password 'manager' since it's not an actual manager and lacks all the cross-platform capabilities of a dedicated app/service like BW, Keepass, you name it.While my colleagues Michael Ansaldo and Alaina Yee have written a full Bitwarden review, I thought I’d relate a bit more about my personal experience with the software, plus some ways to make it work even better. To my knowledge, as long as you stick with Chrome and Google's password 'manager', you are fine since you are inside their walled garden (hold on, that reminds me something!).

That's kind of sad tho to see how Google is giving less and less importance to issues that don't affect its own services. If it works Imma ask you for your paypal info since I would gladly offer you a beer. I will post an update here once Chrome Canary includes the patch.įabian, I'm super eager to test your patch. I have submitted patches to both Chromium and the Android Open Source Project that should resolve this issue. I thought I found a pattern of working twice before needing a relaunch of Chrome, but upon further testing it seems to still be basically random. Unfortunately, this is also a problem even with the new autofill API in Android 11.

Hmm, I thought that it was already established that my device has file-based encryption, not full-disk encryption as in your tests, and that there's at least a theoretically proven exploit for my device if I enable any accessibility services. At this point, you should be fine with both the accessibility service and encryption (tried with other devices still featuring full disk encryption). Just turn on Bitwarden and then set up the PIN again and enable 'Secure Startup' when asked. Obviously I haven't enabled the Accessibility Service not even once because of this warning message. If my personal locking mechanism isn't used, then what is, some default encryption key? Doesn't sound that secure to me. If you turn on Bitwarden, your device won't use your screen lock to enhance data encryption. On my Android 9 device, when trying to enable the Bitwarden Accessibility Service, I'm greeted with this warning: Since Android 7.0, Android uses file-based rather than full-disk encryption, which allows accessibility services to run at boot without affecting the level of encryption of user files.

Bitwarden autofill android