3 ms·

Does it have the following? They're what have kept me stuck on KeePass: - Browser integration (a single key combo unlocking & filling in passwords) - OTP supp

Does it have the following? They're what have kept me stuck on KeePass: - Browser integration (a single key combo unlocking & filling in passwords) - OTP support - SSH agent and key storage - Entry-level (rather than file-level) synchronization - Google Drive synchronization - Automatic history maintenance - Storing arbitrary additional data - Icons (makes identifying entries so much faster)

steve19 8y ago
It has browser integration but it has a client server model so there is nothing to sync with gdrive or Dropbox. So it's more like lastpass than keypass. You can host your own server and there is at least one alternative server implementation.
maccard 8y ago
It does have a decent browser integration, OTP support, history support (last 5 passwords) support for arbitrary additional data and icons. Having not read the source code, or investigated the details, my understanding is the sync is entry based over file based. On multiple occasions I lost data to Keepass's insane lack of sync functionality, I've never once done the same with Bitwarden. Google drive sync is kind of moot as the sync happens on a server (which you can run yourself).
- mehrdadn 8y ago
  > my understanding is the sync is entry based over file based > Google drive sync is kind of moot as the sync happens on a server Confused, so are you saying there is a server that does entry-based syncing? KeePass it's the KeePass client that resolves conflicts at the entry level with whatever is on Google Drive (which it connects to via plugins).
  - maccard 8y ago
    Apologies, I spoke too quickly. I'm unable to edit my original post to fix it. The sync is client side according to [0]. I can't find specifics in any documentation on whether it works at an entry or file level, however I wonder is that actually important? Just because you sync at a file granularity doesn't mean you can't resolve entries individually. My experience with Keepass was that my changes would get stuck in a conflict file that Dropbox would generate if you happened to use Keepass in 2 places at once, as they don't support syncing and force you to manually go through [1] on every device. [0]https://help.bitwarden.com/article/how-is-data-securely-transmitted-and-stored/ https://help.bitwarden.com/article/how-is-data-securely-tran... [1]https://gist.github.com/cmcginty/07869f3c6c27ecb0fef84ca7900e7bb7 https://gist.github.com/cmcginty/07869f3c6c27ecb0fef84ca7900...
    - mehrdadn 8y ago
      I was using "syncing" and "resolving" synonymously. What I was distinguishing between was keeping the most recent file (which is what happens if you use typical cloud syncing for the whole database file) vs. the most recent entry in a given file (which is what you get when KeePass itself gets a chance to actually examine both versions and figure out conflicts internally). I can't figure out how the KeePass (or the plugin you use, or whatever it is) was handling your Dropbox syncing; it sounds like it was doing a dumb file-level merge, when in fact it's capable of doing much better than that. I use the Google Sync Plugin which has never failed me, even when I'd modified databases on two clients independently before syncing. It uses the ImportUtil.Synchronize() function which I think is what handles the dirty details. See the Technical Details section here: https://keepass.info/help/v2/sync.html https://keepass.info/help/v2/sync.html
      - maccard 8y ago
        > What I was distinguishing between was keeping the most recent file vs. the most recent entry in a given file Sure! (sorry, have finally had my morning coffee). I believe that Bitwarden handles it correctly via "live sync" [0]. - albeit it's been a transparent process to me. I've generated logins on my mobile, and logged into them within 30s via the browser extensions on my desktop PC. > I can't figure out how the KeePass (or the plugin you use, or whatever it is) was handling your Dropbox syncing;it sounds like it was doing a dumb file-level merge It was, and it was excruciating. However, this is one of the issues I have with Keepass - it may be possible to do better, but the default behaviour is abhorrent. From the link you gave, it explicitly calls out the issue in "advanced" synchronisation schemes under "Local <-> Master" [1]. If you don't correctly follow the setup steps you can end up with [2] which can (and does) result in data loss. The (as far as I can tell) official (as far as I can tell) forums seem to be happy to pass the buck [3] and say "Oh that's not our problem, that's the sync services problem". > I use the Google Sync Plugin which has never failed me I don't doubt that for a minute, but for someone migrating from LastPass/OnePass to Keepass, searching for "How to sync keepass across machines" will _never_ point you to the google sync plugin. [0] https://blog.bitwarden.com/live-sync-bitwarden-apps-fb7a54569fea https://blog.bitwarden.com/live-sync-bitwarden-apps-fb7a5456... [1] https://keepass.info/help/kb/trigger_examples.html#dbsync https://keepass.info/help/kb/trigger_examples.html#dbsync [2] https://sourceforge.net/p/keepass/discussion/329221/thread/22255c46/ https://sourceforge.net/p/keepass/discussion/329221/thread/2... [3] https://sourceforge.net/p/keepass/discussion/329221/thread/9deb1dc3/ https://sourceforge.net/p/keepass/discussion/329221/thread/9...
odensc 8y ago
- Browser integration (a single key combo unlocking & filling in passwords) Yes. - OTP support Yes. - SSH agent and key storage No. - Entry-level (rather than file-level) synchronization Yes. - Google Drive synchronization Nope, but because it's hosted (or self-hosted) that's inapplicable. - Automatic history maintenance Yes, if you're talking about password history. - Storing arbitrary additional data Yes, including files. - Icons (makes identifying entries so much faster) Yes.

steve19 8y ago

It has browser integration but it has a client server model so there is nothing to sync with gdrive or Dropbox. So it's more like lastpass than keypass. You can host your own server and there is at least one alternative server implementation.

maccard 8y ago

It does have a decent browser integration, OTP support, history support (last 5 passwords) support for arbitrary additional data and icons. Having not read the source code, or investigated the details, my understanding is the sync is entry based over file based. On multiple occasions I lost data to Keepass's insane lack of sync functionality, I've never once done the same with Bitwarden. Google drive sync is kind of moot as the sync happens on a server (which you can run yourself).

mehrdadn 8y ago
> my understanding is the sync is entry based over file based > Google drive sync is kind of moot as the sync happens on a server Confused, so are you saying there is a server that does entry-based syncing? KeePass it's the KeePass client that resolves conflicts at the entry level with whatever is on Google Drive (which it connects to via plugins).
- maccard 8y ago
  Apologies, I spoke too quickly. I'm unable to edit my original post to fix it. The sync is client side according to [0]. I can't find specifics in any documentation on whether it works at an entry or file level, however I wonder is that actually important? Just because you sync at a file granularity doesn't mean you can't resolve entries individually. My experience with Keepass was that my changes would get stuck in a conflict file that Dropbox would generate if you happened to use Keepass in 2 places at once, as they don't support syncing and force you to manually go through [1] on every device. [0]https://help.bitwarden.com/article/how-is-data-securely-transmitted-and-stored/ https://help.bitwarden.com/article/how-is-data-securely-tran... [1]https://gist.github.com/cmcginty/07869f3c6c27ecb0fef84ca7900e7bb7 https://gist.github.com/cmcginty/07869f3c6c27ecb0fef84ca7900...
  - mehrdadn 8y ago
    I was using "syncing" and "resolving" synonymously. What I was distinguishing between was keeping the most recent file (which is what happens if you use typical cloud syncing for the whole database file) vs. the most recent entry in a given file (which is what you get when KeePass itself gets a chance to actually examine both versions and figure out conflicts internally). I can't figure out how the KeePass (or the plugin you use, or whatever it is) was handling your Dropbox syncing; it sounds like it was doing a dumb file-level merge, when in fact it's capable of doing much better than that. I use the Google Sync Plugin which has never failed me, even when I'd modified databases on two clients independently before syncing. It uses the ImportUtil.Synchronize() function which I think is what handles the dirty details. See the Technical Details section here: https://keepass.info/help/v2/sync.html https://keepass.info/help/v2/sync.html
    - maccard 8y ago
      > What I was distinguishing between was keeping the most recent file vs. the most recent entry in a given file Sure! (sorry, have finally had my morning coffee). I believe that Bitwarden handles it correctly via "live sync" [0]. - albeit it's been a transparent process to me. I've generated logins on my mobile, and logged into them within 30s via the browser extensions on my desktop PC. > I can't figure out how the KeePass (or the plugin you use, or whatever it is) was handling your Dropbox syncing;it sounds like it was doing a dumb file-level merge It was, and it was excruciating. However, this is one of the issues I have with Keepass - it may be possible to do better, but the default behaviour is abhorrent. From the link you gave, it explicitly calls out the issue in "advanced" synchronisation schemes under "Local <-> Master" [1]. If you don't correctly follow the setup steps you can end up with [2] which can (and does) result in data loss. The (as far as I can tell) official (as far as I can tell) forums seem to be happy to pass the buck [3] and say "Oh that's not our problem, that's the sync services problem". > I use the Google Sync Plugin which has never failed me I don't doubt that for a minute, but for someone migrating from LastPass/OnePass to Keepass, searching for "How to sync keepass across machines" will _never_ point you to the google sync plugin. [0] https://blog.bitwarden.com/live-sync-bitwarden-apps-fb7a54569fea https://blog.bitwarden.com/live-sync-bitwarden-apps-fb7a5456... [1] https://keepass.info/help/kb/trigger_examples.html#dbsync https://keepass.info/help/kb/trigger_examples.html#dbsync [2] https://sourceforge.net/p/keepass/discussion/329221/thread/22255c46/ https://sourceforge.net/p/keepass/discussion/329221/thread/2... [3] https://sourceforge.net/p/keepass/discussion/329221/thread/9deb1dc3/ https://sourceforge.net/p/keepass/discussion/329221/thread/9...

odensc 8y ago

- Browser integration (a single key combo unlocking & filling in passwords) Yes. - OTP support Yes. - SSH agent and key storage No. - Entry-level (rather than file-level) synchronization Yes. - Google Drive synchronization Nope, but because it's hosted (or self-hosted) that's inapplicable. - Automatic history maintenance Yes, if you're talking about password history. - Storing arbitrary additional data Yes, including files. - Icons (makes identifying entries so much faster) Yes.