The assumption is that the native passkey manager on the device (iPhone, android, windows) would sync the passkeys (to Apple , Google, Microsoft) for protection against device failure and easy of use across devices. Or you risk loosing your accounts if you loose your device.
Dont they all sync to the respective cloud services?
iOS vault -> synced apple cloud
Android vault -> synced with Google cloud?
Windows Hello -> synced with Microsoft account?
And if they’re not synced, that’s even worse. Loose your device and loose your account. Or keep track of which of your 5 devices are have keys for which of your 150 accounts
A cursory search lead to this thread from 2024 https://community.bitwarden.com/t/concerns-over-bitwarden-moving-away-from-open-source-what-does-our-future-hold/74800
where an employee stated
I’ll note that policy wise nothing changed. The referenced issue is a packaging bug, but the goal still is the dual licensing model, with the core being open source, and some (mostly enterprise) features being source-available.
Both the client and server are mostly open source. Some server features are paywalled. The alternative Vaultwarden server is fully open source, and much lighter on system resources.
Have there been any recent licensing shenanigans with BitWarden?
A key for each service for each device is too impractical in real life.
Getting a new device would mean logging in to hundreds of services to link up the new device. Or somehow keep track of which services have keys with which devices. And signing up to a new service would mean having to remember to generate keys for a a handfull of devices, some of which might not be available at the time (like a desktop computer at home when you are out). Or you risk getting logged out if you loose the one device that had a key for that particular service.
I agree passkeys can make sense with something like BitWarden or KeyPassX. Something that is FOSS, and is OS and device agnostic, and let’s you sync keys across devices. And should have independent backups too. Sync is not backup.
I use BitWarden too. OS , device and browser agnostic is a win
But I imagine the vast amount of people will use whatever their platform is pushing, so Apple Google or Microsoft. And in 5 years time “3rd party passkeys” are not “secure enough” and blocked by the OS. (Ok that’s a bit tinfoil hat, but Google’s recent Android app developer verification scheme is fresh in mind)
The biggest disadvantage:
Disadvantages of Passkeys
Ecosystem Lock-In – Passkey pairs are synced through each vendor’s respective clouds via end-to-end encryption to facilitate seamless access multiple devices.
More eggs in the American megacorp basket for more people, yay
Didnt the article say they retrieved the filename and hash, thus proving the existence of the crash diagnostic snapshot. After which Tesla handed over their copy?
Or did the forensics retrieve the actual data?
Edit: Given the importance of this type of data, not saving it to non-voletile memory is negligent at best. Even if it required a huge amount of space, they could delete unimportant files like the Spotify cache or apps or whatever
There is a big push from EU at the moment to reduce “red tape” to make it easier for business, see for example mastodon post from EC a few hours ago: https://ec.social-network.europa.eu/@EUCommission/114280068967975617
How come?
deleted by creator
Difference is timescale. Coal “sequestered carbon” over millions of years, and released over a few decades.
Biomass gathers and realeases on the same timescale
From the article:
In a statement, the police in Finland said the authorities had boarded the Eagle S tanker in Finnish waters.
So no international waters in this case. In fact there are no international waters in the Baltic Sea ( https://en.m.wikipedia.org/wiki/International_waters )
I chuckled a bit when seeing this headline. “Really? 4usd per usg? So cheap. That’s what all this fuel crisis is about?”