Yes, I use BitWarden for personal and business.
You can modify in the settings how long a particular instance of BitWarden is open before it locks, and what you have to do once that happens (just enter PW vs redo the full login with 2FA).
The LastPass breach was particularly bad. Although what happened to LastPass could happen to any cloud-based PW management software, the lack of transparency surrounding what happened was an example of what not to do.
Allegedly, users' encrypted vaults were taken. If that's accurate, eventually someone is going to attempt to brute force your LastPass vault open, if they haven't already. You need to operate under the assumption that all of your PWs were compromised and update them all after the migration to BitWarden. As tedious as that is, it's a no-brainer given what happened.
And, enable time-factor 2FA with both Bitwarden and any site that allows it. Authy is a good one for most people. I used to use that but now use Aegis. I wouldn't recommend Aegis unless you're tech savvy and doing backups of your 2FA seeds yourself doesn't scare you.
lenraphael wrote:After that calmed down, a lot of my three field site login fields didn't convert. I'm guessing I'll have to create a bunch of "custom" fields for those multi field login sites.? LP did that automatically.
Can you give an example? If you right click on a login field or checkbox ("Remember my username" etc), go down to the BitWarden menu and you'll see an option to copy the custom field name. Then you can create a rule for what happens to that custom field when you autofill with BitWarden.
For example, I have rules to uncheck all of those "Keep me logged in", "Remember my username", etc boxes if they're checked by default.