Is Bitwarden making the same mistakes as LastPass?

  • SpinRite v6.1 Release #3
    The 3rd release of SpinRite v6.1 is published and may be obtained by all SpinRite v6.0 owners at the SpinRite v6.1 Pre-Release page. (SpinRite will shortly be officially updated to v6.1 so this page will be renamed.) The primary new feature, and the reason for this release, was the discovery of memory problems in some systems that were affecting SpinRite's operation. So SpinRite now incorporates a built-in test of the system's memory. For the full story, please see this page in the "Pre-Release Announcements & Feedback" forum.
  • Be sure to checkout “Tips & Tricks”
    Dear Guest Visitor → Once you register and log-in please checkout the “Tips & Tricks” page for some very handy tips!

  • BootAble – FreeDOS boot testing freeware

    To obtain direct, low-level access to a system's mass storage drives, SpinRite runs under a GRC-customized version of FreeDOS which has been modified to add compatibility with all file systems. In order to run SpinRite it must first be possible to boot FreeDOS.

    GRC's “BootAble” freeware allows anyone to easily create BIOS-bootable media in order to workout and confirm the details of getting a machine to boot FreeDOS through a BIOS. Once the means of doing that has been determined, the media created by SpinRite can be booted and run in the same way.

    The participants here, who have taken the time to share their knowledge and experience, their successes and some frustrations with booting their computers into FreeDOS, have created a valuable knowledgebase which will benefit everyone who follows.

    You may click on the image to the right to obtain your own copy of BootAble. Then use the knowledge and experience documented here to boot your computer(s) into FreeDOS. And please do not hesitate to ask questions – nowhere else can better answers be found.

    (You may permanently close this reminder with the 'X' in the upper right.)


New member
Jan 23, 2023
Here are two articles pointing out weaknesses in Bitwarden's architecture that are very similar to those discovered with LastPass. They describe apparent weaknesses in the vault encryption architecture and the use of PBKDF2 with a relatively low iteration count for master passwords.

There is also a reddit thread discussing these, in which one developer states that Bitwarden is working to address these issues. But others are saying the issues have been known for a while with no action from Bitwarden.

This seems significant given that many left LastPass for Bitwarden due to LastPass's similar issues. I'd be interested to hear people's thoughts.
I am sure that @Steve covered the fact that the secret that is the vault password hash is being hashed 100'100 times server side too:
LastPass receives the Login Hash from the user (following the default 100,100 iterations on the user’s Master Password using PBKDF2-SHA256), the Login Hash is additionally salted with a random 256-bit salt, and an additional 100,000 rounds of PBKDF2-SHA256 are performed. That output is then hashed using scrypt to increase the memory requirements of brute-force attacks. The resulting hash stored by LastPass is the output of 200,101 rounds of SHA256 + script.

Bitwarden leaves less metadata in the clear - so no easy access to websites stored, for example.

What's clear is when you put all of your eggs into one basket, any flaw in that basket will put you at risk.

Bitwarden allows a max of 2 million iterations for the vault. Couple that with high entropy password and for the greater brute-forcing protection of the application layer, MFA, and you should be later in the queue to become a victim than many others.

After all, when you're being chased by a lion, you don't have to be the fastest runner, you just have to be faster than the slowest runner....