4 ms·

Not related to the fundraising, but a more general question I've had about password managers for a while: Why does anyone pay a subscription for their password

by hbn 4y ago

Not related to the fundraising, but a more general question I've had about password managers for a while: Why does anyone pay a subscription for their password manager when all you need is a client that talks to any old free cloud storage service (Dropbox, iCloud, Google Drive, etc)? I feel like I might be grandfathered in and they switched to a new model now, but I got Enpass years ago and haven't paid since. I sync my password archive through iCloud so I don't have to trust a random company to store my password archive safely. If anything, by doing that you're centralizing a ton of user logins in a single place that would be a great target if you found a way to hack in and read them.

jlund-molfese 4y ago
Sync conflicts are pretty common with KeePassXC on Dropbox (iCloud, Google Drive are not viable options on Linux). I also didn't want to run the Dropbox client just to sync passwords. Paying Bitwarden $10/year made sense to me.
- mdaniel 4y ago
  In my experience, sync conflicts are pretty common on SyncThing, too, which is often how I hear this paired ("use KeePassXC on Syncthing for the win" type deal) I think it's an impedance mismatch trying to take a single-user database format and trying to use it from multiple devices
- hbn 4y ago
  Why would you need to run the Dropbox client to sync your passwords? Shouldn't the password manager client be able to talk to the service directly? I don't have an iCloud client installed on my devices (well, other than whatever is built into Apple devices) but Enpass just uses their APIs to sync passwords. Occasionally I have to reauthenticate on one of my machines but it tells me as soon as it loses access. Previously I synced it over Google Drive and I never installed a Google Drive client either.
  - jlund-molfese 4y ago
    It's totally possible, but that sounds like it would cost a lot of development time. The KeePassXC project in particular decided not to implement cloud connectors due to a lack of resources.
    - hbn 4y ago
      I'm not sure why you think this is that difficult of a task. This is standard fare for how clients integrate with a service. There's how many third party Twitter and Reddit clients out there, plenty made by a single person that just communicates with a public API made for integration. You can spin up a Discord bot in a few minutes. Why is this any different for syncing a file over an API?

by hbn 4y ago

jlund-molfese 4y ago

Sync conflicts are pretty common with KeePassXC on Dropbox (iCloud, Google Drive are not viable options on Linux). I also didn't want to run the Dropbox client just to sync passwords. Paying Bitwarden $10/year made sense to me.

mdaniel 4y ago
In my experience, sync conflicts are pretty common on SyncThing, too, which is often how I hear this paired ("use KeePassXC on Syncthing for the win" type deal) I think it's an impedance mismatch trying to take a single-user database format and trying to use it from multiple devices
hbn 4y ago
Why would you need to run the Dropbox client to sync your passwords? Shouldn't the password manager client be able to talk to the service directly? I don't have an iCloud client installed on my devices (well, other than whatever is built into Apple devices) but Enpass just uses their APIs to sync passwords. Occasionally I have to reauthenticate on one of my machines but it tells me as soon as it loses access. Previously I synced it over Google Drive and I never installed a Google Drive client either.
- jlund-molfese 4y ago
  It's totally possible, but that sounds like it would cost a lot of development time. The KeePassXC project in particular decided not to implement cloud connectors due to a lack of resources.
  - hbn 4y ago
    I'm not sure why you think this is that difficult of a task. This is standard fare for how clients integrate with a service. There's how many third party Twitter and Reddit clients out there, plenty made by a single person that just communicates with a public API made for integration. You can spin up a Discord bot in a few minutes. Why is this any different for syncing a file over an API?