this post was submitted on 28 Feb 2025
553 points (93.5% liked)

memes

16673 readers
3522 users here now

Community rules

1. Be civilNo trolling, bigotry or other insulting / annoying behaviour

2. No politicsThis is non-politics community. For political memes please go to !politicalmemes@lemmy.world

3. No recent repostsCheck for reposts when posting a meme, you can only repost after 1 month

4. No botsNo bots without the express approval of the mods or the admins

5. No Spam/Ads/AI SlopNo advertisements or spam. This is an instance rule and the only way to live. We also consider AI slop to be spam in this community and is subject to removal.

A collection of some classic Lemmy memes for your enjoyment

Sister communities

founded 2 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] lmmarsano@lemmynsfw.com 1 points 5 months ago

loaded an HTML login page that had no discernable controls to use that Bitwarden passkey; expecting entirely for it to exist in my Apple keychain, which I never use

I use Bitwarden, yet not macOS/iOS. Whenever a passkey dialog from the wrong authenticator comes up, I choose option other to redirect to a device running Bitwarden: I see macOS & iOS offer similar controls. However, Bitwarden's passkey dialog (section with links to configuring that) usually pops up, so that isn't necessary.

But if that’s the case, how can I guarantee any other accounts I move over won’t fuck it up somewhere?

Save a recovery code in Bitwarden (add field type hidden named Recovery code to the login entry)? That's standard practice for me, though I've never needed them.

I haven’t seen anyone get the concept of passwords wrong

I have control of the copy-paste function and can even type a password myself if needed

I've seen forms disable paste. Much can go wrong with passwords. Passwords require sharing & transmitting a secret (a symmetric key), which either party can fail to secure. Passkeys, however, never transmit secrets. Instead, they transmit challenges using asymmetric cryptography. The application can't fail to secure a secret it never has. Far more secure, and less to go wrong.

The password field is a more manual, error prone user interface. With passkeys/WebAuthn, you instead supply a key that isn't transmitted: easier than passwords when setup correctly, & nothing to do until it's setup correctly.

Similar situation with ssh: though it can accept passwords, ssh key authentication is way nicer & more secure.