![]() ![]() ![]() ![]() |
|
mjb:ANglEAUT: PS Anybody use their PW manager with a QNAP NAS. I can't get Bitwarden to identify the username field. It just stays bank.
Custom field, "username" in the "name" field, and your NAS username in the "value" field.
Nah, doesn't work for me.
Please keep this GZ community vibrant by contributing in a constructive & respectful manner.
OWASP just changed their recommendation for PBKDF2 work factors (iterations) to 600,000 (thanks to LastPass).
So, LastPass posted that their iteration count was set to 100,100: https://support.lastpass.com/help/about-password-iterations-lp030027 but, this turned out to be false with many customers reporting they were set to as low as 1 iteration but the most common iteration counts were 500 & 5000. Customers were not upgraded automatically meaning their vaults could be brute forced easily.
Bitwarden's older customers were set to 100,001 but in response to the recommendation from OWASP newer accounts are set to 350,000 iterations. They're still considering upgrading existing customers but you can do this yourself in your web vault under Security --> Keys (I upgraded mine to 350,000 as I found 600,000 was actually quite slow) - https://fosstodon.org/@bitwarden/109733968664841286
I encourage everyone using Bitwarden to up their security by setting your KDF iterations to 350,000.
Michael Murphy | https://murfy.nz
Referral Links: Quic Broadband (use R122101E7CV7Q for free setup)
Are you happy with what you get from Geekzone? Please consider supporting us by subscribing.
Opinions are my own and not the views of my employer.
Done - thanks for the tip.
michaelmurfy:
OWASP just changed their recommendation for PBKDF2 work factors (iterations) to 600,000 (thanks to LastPass).
So, LastPass posted that their iteration count was set to 100,100: https://support.lastpass.com/help/about-password-iterations-lp030027 but, this turned out to be false with many customers reporting they were set to as low as 1 iteration but the most common iteration counts were 500 & 5000. Customers were not upgraded automatically meaning their vaults could be brute forced easily.
This post from 5 years ago says that existing customers would be upgraded to the new default 100,100 and they didn't need to do anything. https://blog.lastpass.com/2018/07/lastpass-bugcrowd-update/amp/
@mattwnz That never actually happened automatically. This is just a single example but there are many many more out there: https://www.reddit.com/r/Lastpass/comments/106p7le/by_default_the_number_of_password_iterations_that/
A person in my team at work had an iteration count of 1 (I work in security also so this was rather shocking to see). Admittedly this was because he never changed his (rather long) master password + used 2FA. The upgrade to 100,100 required a user to update their master password.
Michael Murphy | https://murfy.nz
Referral Links: Quic Broadband (use R122101E7CV7Q for free setup)
Are you happy with what you get from Geekzone? Please consider supporting us by subscribing.
Opinions are my own and not the views of my employer.
JFC: https://www.theverge.com/2023/1/24/23569109/goto-hack-lastpass-breach-encrypted-backups-key
I could hope the fact I haven't been contacted yet is a good sign, but suspect that could also be down to simple omnishamblery.
Time to accelerate BW transition. 350K iterations already set.
oof, makes me glad I followed a recommendation to use 1password years ago.
The almost secure articles on password managers make for interesting reading, even if I understand little of it.
My genuine concern is that LP and said parent company may simply fold before I can get all my stuff off there and switched over to something else, in which case I lose the list of what may or may not be later compromised.
mattwnz:
michaelmurfy:
OWASP just changed their recommendation for PBKDF2 work factors (iterations) to 600,000 (thanks to LastPass).
So, LastPass posted that their iteration count was set to 100,100: https://support.lastpass.com/help/about-password-iterations-lp030027 but, this turned out to be false with many customers reporting they were set to as low as 1 iteration but the most common iteration counts were 500 & 5000. Customers were not upgraded automatically meaning their vaults could be brute forced easily.
This post from 5 years ago says that existing customers would be upgraded to the new default 100,100 and they didn't need to do anything. https://blog.lastpass.com/2018/07/lastpass-bugcrowd-update/amp/
I can confirm this was NOT done. Mine was set to 5000 and not upgraded by LastPass.
michaelmurfy:
...but you can do this yourself in your web vault under Security --> Keys
I encourage everyone using Bitwarden to up their security by setting your KDF iterations to 350,000.
Done.
Also got around to cancelling my LastPass subscription and deleting my vault. Feels good to have complete separation.
For those that have migrated to BitWarden:
I have some passwords saved for various sites that I also have additional Notes added to. So in LastPass under the site password I can see username, password, and then another field at the bottom called NOTES. In some cases I will need those notes, for example if you have a RealMe account you also need to have created a PIN for when you ever need to change/recover your password. I put things like this into the NOTES field for each password entry.
Does BitWarden import NOTES into their saved site passwords? Or will I need to go through each site and check if there were any notes and manually make an entry somewhere in BitWarden.
duckDecoy:
For those that have migrated to BitWarden:
I have some passwords saved for various sites that I also have additional Notes added to. So in LastPass under the site password I can see username, password, and then another field at the bottom called NOTES. In some cases I will need those notes, for example if you have a RealMe account you also need to have created a PIN for when you ever need to change/recover your password. I put things like this into the NOTES field for each password entry.
Does BitWarden import NOTES into their saved site passwords? Or will I need to go through each site and check if there were any notes and manually make an entry somewhere in BitWarden.
Yep, both notes to logins/passwords and separate secure notes seem to transfer with the export from LP / import to BW default settings. This is based on a random survey of things I have notes for, I've not been through everything exhaustively (I have another 6 months on my LP subscription just in case anything is missing and I do need to get back to that). All in all, the transition was shockingly easy - I had expected much more pain than this.
GV27:
My genuine concern is that LP and said parent company may simply fold before I can get all my stuff off there and switched over to something else, in which case I lose the list of what may or may not be later compromised.
You can export from Lastpass to a CSV right now. Not at all secure obviusly but potentially better than the alternative.
OK, took the dive into Bitwarden. Exported Lastpass to CSV and had a big cleanout of old cr*p. Imported into BW. Could not be easier. Added Google Authenticator. So far so good.
Next thing would be to avoid having to enter the long Master Password on every autofil on IOS. How do I do that?
|
![]() ![]() ![]() ![]() |