Android-Password-Store VS clients

There is no "database", it's just a bunch of GPG encrypted files synced with git.

For Android there is https://github.com/android-password-store/Android-Password-S....

For Windows the only thing (Pass4Win) i found is unmaintained.

See https://www.passwordstore.org/#other

These are the types of applications that I really love. It stores the data in a cloud service that already has enough free capacity for say a notes app. It's like how we can store pass(1) passwords on a git repository (Sync it with Github) and use that as the destination of Android Password Store[1], and you have a easy password manager.

[1] https://github.com/android-password-store/Android-Password-S...

Password manager -Android-password-store (client for pass)

Since I store most of my passwords using https://www.passwordstore.org/, I have used mobile with https://github.com/android-password-store/Android-Password-S.... I'm happy enough with it. Sucks for getting anything into consoles, for obvious reasons.

I use Password Store.

That's the exact setup I use on my main phone. There's also https://github.com/android-password-store/Android-Password-S..., which I use on throwaway phones.

The pass command makes this significantly easier:

https://www.passwordstore.org/

There's even a decent Android client:

https://github.com/android-password-store/Android-Password-S...

There are Pass-compatible apps for iOS, Android, Windows, etc. I use Password Store on Android and QtPass on Windows.

I didn't go chasing through all the typescript but I'd presume adding a new PassphraseGenerationStrategy https://github.com/bitwarden/clients/blob/desktop-v2024.3.0/...

Breaking: Open Source software have BUGS!

https://github.com/bitwarden/clients/issues/6560#issuecommen...

Bug fix for this has been merged last week. It is not in 2023.10 though, so you will have to wait for the next release of the web vault.

It's definitely out (https://github.com/bitwarden/clients/releases/tag/browser-v2... just looks like browsers haven't approved it yet.

I'm not sure about any specifics beyond that both are getting support for them (for the keepass ecosystem I'm sure about other mobile clients, but I don't think the feature request to support passkeys has been acknowledged by the keepass2android dev sadly). Here's the keepassxc PR with some details about the implementation, and what should be done in future work on passkey support: https://github.com/keepassxreboot/keepassxc/pull/8825

Bitwarden has a few blogs if you search for bitwarden passkeys, but from skimming one it didn't seem to go into technical details (though I didn't watch the videos). I guess you could look through the PRs: https://github.com/bitwarden/clients/pulls?q=is%3Apr+passkey... but I don't really feel like doing that.

Bitwarden has regular external audits (here is the 2022 audit) and the code (both server side and client side) is open source (here f.e).

/bitwarden_license directory

Now the secret manager is in the `bitwarden_license` directory so it is not a GPL covered product and not open source but covered by BITWARDEN LICENSE AGREEMENT [3]. It does not allow you to use it as OSS.

[1] https://github.com/bitwarden/clients/tree/master/bitwarden_l...

There are apparently known problems (GitHub Issues #5807) in both Edge and FireFox with this newly released browser extension update (2023.7.0), which should hopefully be fixed soon. In the meantime, on Edge, you can revert to version 2023.5.1 for Chromium, which is still available from the Google Chrome store: