4 ms·

I've found the multi device syncing easier and the integration with iOS works very well.

teekert 5y ago
This was my reason to go away from KeePass(XC) with NextCloud for sync. I would inevitably run into a sync issues (also due to the need for NextCloud to be always up of course, also self-hosted) and I never found a nice way to integrate KeePassXC into android or iOS, Bitwarden just works, on any OS (allthough what I find annoying is that you have to sync the vault before you get new stuff by going into the app and syncing, just using it does not update it, so frequently I find myself missing passwords on iOS and then I need to manual sync first). Oh, and there is an issues with using it in private tabs on FireFox which has existed since I started using it.
- toyg 5y ago
  > you have to sync the vault before you get new stuff I had that problem on iOS, and it disappeared since I moved to Android. There is probably an issue in what they are (not) allowed to do in background on iOS.
- jptech 5y ago
  > I would inevitably run into a sync issues Could it be that you weren't using it correctly? KeePass database files aren't supposed to remain open (for security of course) and it has quite a number of options to automatically close it after certain amount of time or when the window isn't focus, computer is locked, etc. This would trigger a sync with the (NC) server and assuming that all your clients follow the same usage pattern and close the DB after a small window of time, there shouldn't be any conflict. > NextCloud to be always up of course, also self-hosted You could use NextCloud's own hosting. But then Bitwarden's server needs to always be up too, and optionally self-hosted. > Bitwarden just works A low bar to recommend a password manager, don't you think so?
  - teekert 5y ago
    My remarks are from the self hosting perspective. To ensure an up-to-date KeePassXC db across all my devices I needed Nextcloud to always be reachable. KeePassXC was not smart about sync, so add one pw on a device before syncing, add one on another and you have two divergent databases that you have to manual reconcile. Bitwarden does not have this issue, and it also keeps itself synced, even if I only set up the add-on in the browser (with KeePassXC you always need the full program installed). With KeePass(XC) it's just an extra layer you need to be aware of, decoupling sync from the db. For me BW has always just worked, meanwhile I have several KeePassXC dbs with a date in their name because of conflicts. Which arguably is because of NextCloud issues, which are my own "fault" (issues include, on work PC file sync services are not allowed, on Server somehow NC disconnects after every container update, since it is "headless" I often notice this very late, the shitty state of NC client packaging on Ubuntu will let you install very old clients that may stop syncing, you need to be aware of this... etc). Perhaps KeePass(XC) just works if you outsource syncing, but then still, it is easier to have sync conflicts than with BW. And then there is the ability to share PWs with relatives with a BW account on the same server, KeePass does not have this concept as far as I am aware.
- tpoacher 5y ago
  My own setup which works beautifully is: KeepassXC on the desktop 'Keepass2Android Offline' on android Keep my database in dropbox. Keep things synced on Android via Dropsync. I know it's not a self-hosted solution, but I think dropbox as a sync solution in this particular case is a pretty good solution for personal use.

This was my reason to go away from KeePass(XC) with NextCloud for sync. I would inevitably run into a sync issues (also due to the need for NextCloud to be always up of course, also self-hosted) and I never found a nice way to integrate KeePassXC into android or iOS, Bitwarden just works, on any OS (allthough what I find annoying is that you have to sync the vault before you get new stuff by going into the app and syncing, just using it does not update it, so frequently I find myself missing passwords on iOS and then I need to manual sync first). Oh, and there is an issues with using it in private tabs on FireFox which has existed since I started using it.

toyg 5y ago
> you have to sync the vault before you get new stuff I had that problem on iOS, and it disappeared since I moved to Android. There is probably an issue in what they are (not) allowed to do in background on iOS.
jptech 5y ago
> I would inevitably run into a sync issues Could it be that you weren't using it correctly? KeePass database files aren't supposed to remain open (for security of course) and it has quite a number of options to automatically close it after certain amount of time or when the window isn't focus, computer is locked, etc. This would trigger a sync with the (NC) server and assuming that all your clients follow the same usage pattern and close the DB after a small window of time, there shouldn't be any conflict. > NextCloud to be always up of course, also self-hosted You could use NextCloud's own hosting. But then Bitwarden's server needs to always be up too, and optionally self-hosted. > Bitwarden just works A low bar to recommend a password manager, don't you think so?
- teekert 5y ago
  My remarks are from the self hosting perspective. To ensure an up-to-date KeePassXC db across all my devices I needed Nextcloud to always be reachable. KeePassXC was not smart about sync, so add one pw on a device before syncing, add one on another and you have two divergent databases that you have to manual reconcile. Bitwarden does not have this issue, and it also keeps itself synced, even if I only set up the add-on in the browser (with KeePassXC you always need the full program installed). With KeePass(XC) it's just an extra layer you need to be aware of, decoupling sync from the db. For me BW has always just worked, meanwhile I have several KeePassXC dbs with a date in their name because of conflicts. Which arguably is because of NextCloud issues, which are my own "fault" (issues include, on work PC file sync services are not allowed, on Server somehow NC disconnects after every container update, since it is "headless" I often notice this very late, the shitty state of NC client packaging on Ubuntu will let you install very old clients that may stop syncing, you need to be aware of this... etc). Perhaps KeePass(XC) just works if you outsource syncing, but then still, it is easier to have sync conflicts than with BW. And then there is the ability to share PWs with relatives with a BW account on the same server, KeePass does not have this concept as far as I am aware.
tpoacher 5y ago
My own setup which works beautifully is: KeepassXC on the desktop 'Keepass2Android Offline' on android Keep my database in dropbox. Keep things synced on Android via Dropsync. I know it's not a self-hosted solution, but I think dropbox as a sync solution in this particular case is a pretty good solution for personal use.