When this first hit the news I started planning my migration. I settled on Enpass https://www.enpass.io/ . The main client is closed source but the password file is an encrypted SQLite database and is readable by open source tools (written in Go https://github.com/hazcod/enpass-cli).
The UI isn't quite as polished as 1Password but it's pretty good, and more consistent/discoverable IMHO.
This was a "small" disruption but with a local file I have more confidence I can avoid disruptions. /wave 1password and hello bitwarden (though I'll be looking at enpass as mentioned in the first comment)
But you can still use 1Password even if the service is temporarily disrupted. You have a local copy of your data on each device, so you can work when you are offline. It's just that your vault is stored in the cloud, so syncing could be disrupted. This thread's headline is misleading IMO.
Why not just use the iCloud one built into iOS/macOS. I know it’s not a single pass key for all your passwords, buts it’s already baked in and works well.
5 comments
[ 5.2 ms ] story [ 22.5 ms ] threadThe UI isn't quite as polished as 1Password but it's pretty good, and more consistent/discoverable IMHO.
However, I like my data local because: https://blog.1password.com/update-on-our-recent-service-disr...
This was a "small" disruption but with a local file I have more confidence I can avoid disruptions. /wave 1password and hello bitwarden (though I'll be looking at enpass as mentioned in the first comment)
Source: https://www.reddit.com/r/1Password/comments/qksvl2/with_stan...