Comment on PSA: the bitwarden clients got an upgrade that makes them incompatible with vaultwarden
SmoothLiquidation@lemmy.world 1 week ago
I found this comment on what happened by dani-garcia, one of the main devs:
The short version is that around 8-ish years ago, Bitwarden changed the way the vault items were structured, and Vaultwarden added some backwards compatibility fields to ensure both old and new versions of the clients worked.
These backwards compatibility fields were supposed to be a temporary measure, but for at least the next three years the clients still required them, until we eventually forgot to keep track of them. At some point between 2021 and today, the clients stopped requiring these backwards compatibility fields, but Vaultwarden was still sending them.
This wasn’t a problem until Bitwarden decided to use the backwards compatibility fields in a completely different way, which caused the clients to crash.
JordanZ@lemmy.world 1 week ago
There’s a reason you don’t do things like that…
Apparently nobody in that software team has heard about Knight Capital. They reused a flag and that coupled with a deployment failure that only lasted ~45 minutes caused an over 400 million dollar loss nearly bankrupting the entire company. Ultimately they ended up combining with another company.
More details
eleijeep@piefed.social 1 week ago
I hadn’t heard of this one before, thanks for posting.