I’ve been aware of Bitwarden for some time, but I’ve shied away from seriously considering it because it didn’t – and still doesn’t – support modifying password information while offline. (Yes, these are mostly theoretical concerns, but I like to err on the side of paranoia when it comes to my passwords.) My reasoning is that, since the KeePass applications function offline and the syncing applications have no concept of what it is they’re syncing, it should be safe enough to avoid potentially unpleasant situations like the sync service knowing a little too much about the password database, or the password manager syncing to something I didn’t authorize. kdbx file across my devices, while using an offline KeePass-compatible Android app. Of course, I couldn’t realistically avoid things like automatic syncing of the password database, so I came up with my own solution of using Box.com to sync the. That has always made me just uncomfortable enough to avoid. While I have no concerns with the security of KeePass itself, the problem is, in order to have the more convenient features like automatic syncing, browser integration, and cross-platform compatibility, I’d have to use various third party tools, forks, implementations, or plugins. That said, I’ve been stuck in the past for a while now.

They encourage the use of complex passwords that you don’t have to remember and that attackers are unlikely to brute-force they help to make credential stuffing attacks effectively obsolete and, these days, they speed up the login processes to various websites using browser extensions and mobile apps.

I’ve been a fan of the idea of password managers for a long time.

Taking a little break from my Meteorological meanderings posts, I wanted to share my experience in switching away from KeePass, which I have used since at least 2007, to Bitwarden, a much more modern open source password manager.

Kdbx to csv