Switched to BitWarden a few months ago from years of using LastPass. Zero regrets... it is in every way better for my use case. Switching wasn't hard either. Even gave BW my money, it is worth supporting them.
Love to hear more about why BitWarden is a safer choice than Lastpass if anyone cares to chime in. Thanks.
LastPass bug leaks credentials from previous site
71–80 of 196 posts
Re: LastPass bug leaks credentials from previous site
#72Earlier quoted context omitted.
> Since they moved to a dedicated app instead of just a plugin on Mac, it is borderline unusable for me. What do you mean? They still have browser extensions for all major browsers.
Unless I am missing it, the only way to install it on Mac now is to install an App that acts as your vault and it installs the plugins. (if I click "Open my Vault" it opens a dedicated LastPass App on my Mac)
1. https://chrome.google.com/webstore/detail/lastpass-free-pass...
Re: LastPass bug leaks credentials from previous site
#73Re: LastPass bug leaks credentials from previous site
#74Earlier quoted context omitted.
I'm avoiding the browser extensions, they seem to be a security nightmare. KeePass and similar are a better way to go, if slightly more labor intensive.
> KeePass and similar are a better way to go, if slightly more labor intensive. Slightly? Just thinking about the synchronization between machines makes this an understatement in my opinion.
Re: LastPass bug leaks credentials from previous site
#75[0] https://support.logmeininc.com/lastpass/help/how-do-i-enable...
Re: LastPass bug leaks credentials from previous site
#76Switched to BitWarden a few months ago from years of using LastPass. Zero regrets... it is in every way better for my use case. Switching wasn't hard either. Even gave BW my money, it is worth supporting them.
Love to hear more about why BitWarden is a safer choice than Lastpass if anyone cares to chime in. Thanks.
Both are based on the same underlying principles (AES encrypted database, encrypted using a slow hash of the master password). Both have been audited professionally. Both have browser extensions whose source code you can read (it is JavaScript, just open the extensions directory). Both support a full array of 2F options.
People are moving from LastPass to BitWarden because it is a better product. Plus many dislike LastPass's owners due to the LogMeIn pricing/business practices (like difficulty cancelling/early cancellation to avoid additional billing/aggressive sales people/etc).
The only advantage BitWarden may have is its backend is open source software and you can run a copy yourself (although most choose not to). If you're running it yourself BitWarden is likely your primary contender. If you aren't the difference is largely academic.
Re: LastPass bug leaks credentials from previous site
#77I've love to switch away from LastPass. I switched to LastPass Families when it came out due to their "digital contingency plan" so family members (or the trusted family attorney) can get access to passwords rather conveniently if I or another family member passes away. At the time, I didn't see that other offerings made this as easy. Any other good options out there for this use case?
1Password has a Families plan for this.
Re: LastPass bug leaks credentials from previous site
#78Switched to BitWarden a few months ago from years of using LastPass. Zero regrets... it is in every way better for my use case. Switching wasn't hard either. Even gave BW my money, it is worth supporting them.
Re: LastPass bug leaks credentials from previous site
#79I have been using enpass, and I'm very satisfied. I was a LastPass user once, but never trusted their security model. Then switched to 1password, but the lack of good multiplatform support and their push to a cloud model made me look for alternatives. What I want is support for Mac, Windows, Linux, and Android; possibly one time payment; and local storage (most important). For syncing I use my own nextpass cloud. Bit…
Re: LastPass bug leaks credentials from previous site
#80This is one reason why I believe that browser based password managers are flawed. I've written about this in the past (link below). These apps are popular with normal people (due to convenience), but long-term, we should not trust web browsers plugins or add-ons as password managers. https://github.com/w8rbt/dpg#why-traditional-password-manage...
The two most common (and successful) attack vectors have been via password reuse and low password quality. Convenience, context aware, device agnostic, browser based, password managers have been successful in convincing the general public to use a password manager at all.
The use of a password manager allows people to have per-site and higher quality (e.g. long/difficult to remember) passwords. This has had a positive impact on people's security.
KeePass and similar "offline" solutions avoids some specific attack vectors. However, both "offline" solutions and browser-based extensions also share a great deal of vectors. For example if bad-ware has local execution inside the user's context, all bets are off (assuming you're running KeePass and the database is decrypted in memory, which you need to in order to retrieve a password).
It is fine to suggest options people feel are superior, but ultimately the conveniences are a security benefit within themselves because people are actually using and sticking to password managers (thus avoiding password re-use/low quality passwords).