pwsafe VS DOMtegrity

Maybe I'm old school, but I don't want a local appliance of sorts or external app host to my passwords. I use https://pwsafe.org/ install the app on whatever device I want. Keep the database file in G Drive so it will always sync or can manually download if needed without installing G Drive. The latter I've not had to do though.

It's an Android port of http://pwsafe.org. PwSafe works on iOS, MacOS, Windows and Linux.

I'd put them all in a disk-on-key install of Password Safe (https://pwsafe.org).

passwordsafe https://pwsafe.org/

My father literally writes cryptography protocols. He's the guy with unique, 32 character alpha-numeric passwords for everything, to the point he has to look them up any time a service updates and loses the login information. He uses a password safe. Literally, it's called Password Safe. It's open-source, looks like it was written in 1995, and perfect. Just don't forget the password to the safe, because you're not hacking your way in.

Personally I use PasswordSafe4 and I backup my password files on my phone and I email myself the file every so often.

For local storage, password safe (https://pwsafe.org/) is good and was designed by Bruce Schneier.

Source code is provided here: https://github.com/toreini/DOMtegrity

For browsers this problem is partially solved as subresources may be integrity checked. Further, there have been proposals like DOMTegrity, that provides a complete solution. For now, yes, full integrity checking isn't done automatically in browser, but it may be done automatically using git or manually as is normally done for any software downloaded not using a package manager or git.