![]() ![]() ![]() |
|
Yesterday I switched from Keepass to Bitwarden and I must say that I really like it. I'm able to use the web version of Bitwarden on my work PC which is otherwise really locked down by our IT people (eg I can't install any software, browser extensions, etc). This was something I couldn't do with Keepass, I had to bring it up on my phone and then manually type the passwords into my work PC.
I also moved to bitwarden today but from lastpass. Thought I'd try the competition before I decide what to do going forward with lastpasses decision to change the free structure.
The move was very easy, within 5 minutes all data transferred and up and running. So far it does the job as well as lastpass
dazhann:
I also moved to bitwarden today but from lastpass. Thought I'd try the competition before I decide what to do going forward with lastpasses decision to change the free structure.
The move was very easy, within 5 minutes all data transferred and up and running. So far it does the job as well as lastpass
Alos moved to Bitwarden today, importing my Lastpass data was very east and I think BitWarden works a little better. It certainly looks better so must be better :-)
Add me to the list of those trying out Bitwarden.
I came to read this post to find recommendations for a new password manager, after reading an article on, and subsequently email from, LastPass on the neutering of its free plan.
Colour me impressed thus far. As others have said, the transition is incredibly fast and hassle-free. Account set up, data transferred, 2FA turned on, Chrome extension added, phone app installed - all in 10-15 minutes.
The main problem I've found is with the first use of a saved site (seems to occur on both computer and mobile) which is that the app will first claim it doesn't have a record for the site; searching for it will find it, and I can then click on 'autofill and save'. Next time accessing that site doesn't require the same rigmarole, but still a bit of a hassle. Looks like it's caused by differences between the URLs in the saved record vs the site accessed.
jonathan18:
The main problem I've found is with the first use of a saved site (seems to occur on both computer and mobile) which is that the app will first claim it doesn't have a record for the site; searching for it will find it, and I can then click on 'autofill and save'. Next time accessing that site doesn't require the same rigmarole, but still a bit of a hassle. Looks like it's caused by differences between the URLs in the saved record vs the site accessed.
There are a few different options you can use for telling Bitwarden how to recognise the sites you're visiting. There's a default option (which defaults to Base Domain so would see www.example.com, example.com, test.example.com, etc all as the same site), but for each individual vault record you can override it and use things like Host, Exact, Starts With, Regular Expression. It's quite flexible.
Wow, what a great product. I've been using Bitwarden for a week or more now and am completely committed to it, paid the $10/yr to donate to the dev's. Am going to even delete my Lastpass data and account.
Opps a bit late to the conversation.
+1 to BitWarden. A long time Keepass user who moved to BitWarden in Sept 2020. Hugely more user friendly across different PCs and browsers and got rid of the hassle of syncing Keepass files. Don't regret the change at all.
2FA in place with BitWarden and any site that allows it.
+1 to Authy for 2FA - being able to register it for use on multiple devices is a real plus.
That said, I still use a password protected browser password manager for a few non-essential sites on my main PC. It's just easier.
Nokia 6110, 6210, 6234, Sony Ericsson XPERIA X1, Huawei Ideos X5 (Windows Mobile), Samsung Galaxy SIII, LG G4, OnePlus 5, iPhone Xs Max (briefly), S21 Ultra. And I thought I hadn't had many phones - but the first one around 1997.
A second reminder email from LastPass triggered another migration to Bitwarden. Other than a different name and icon they are so similar in how they work so a perfectly flat learning curve.
|
![]() ![]() ![]() |