This is the issue.

I can’t adopt Passkeys if I’m not certain they’re going to work as well as my password manager and Authenticator app, which is to say 100% of the time.

When sites ask to set up passkeys, it’s usually native passkeys (especially on iOS). And figuring out how to get the flow to set up a LastPass key by default seems unusually difficult.

I also use a MacBook, windows desktop, an iPhone and iPad. I use Firefox, edge, brave across these devices.

When I say “passkeys are a trap” they are a usability trap where no one can attest with certainty that I won’t wake up in a painful situation because I decided to adopt passkeys.

▲

manwe150 an hour ago | parent | next [-]

I’ve never seen an implementation where passkeys deleted my password or could lead to a situation where it was locked out. They usually just bypass the password+2fa dance when functioning, and otherwise just don’t matter if they don’t function. (Well perhaps except home depot, where it gets mad at me every time I use a password and tries to install a new copy of the same broken passkey as last time, for my convience)

▲

Barbing 2 hours ago | parent | prev | next [-]

> no one can attest with certainty that I won’t wake up in a painful situation because I decided to adopt passkeys

Seems that way. Better luck next year, passkey standards(?) people. Hope it’ll be ironed out at some point.

	▲	pirates an hour ago \| parent [-]
		I think the repeated posts and articles constantly rehashing this topic is telling. Every thread is nearly the same in terms of some people saying “here are the reasons why passkeys don’t work for me” and other people saying “you’re holding it wrong”. I don’t think many people come away with their views changed.

▲

xd1936 an hour ago | parent | prev | next [-]

This sounds like an iOS problem. Bitwarden + Firefox on Linux, or Bitwarden + Android, has never been anything but smooth for me when it comes to saving or using Passkeys.

	▲	WorldMaker a few seconds ago \| parent \| next [-]
		iOS has really good support for third party Password Managers. I've seen the integration with both Strongbox and 1Password. I've heard Bitwarden supports it as well. I think it is a Lastpass problem in this specific case.
	▲	kmac_ 31 minutes ago \| parent \| prev \| next [-]
		If we go for anecdotal examples that are not representative, then in my case, Bitwarden passkey use ends in an endless loop with most websites. Import and export is still a promise or "coming soon." In the case of hardware keys, two devices are needed. I was a proponent of passkeys, but big players screwed that up, like every single shared "standard".
	▲	kritr 24 minutes ago \| parent \| prev [-]
		Bitwarden / ProtonPass + iOS has also been smooth. So sounds like a lastpass issue.

▲

ylk 2 hours ago | parent | prev [-]

LastPass has a tutorial video that shows you how to only use them for autofill: https://www.lastpass.com/features/autofill/iphone

Other password managers do, too: https://bitwarden.com/help/auto-fill-ios/#keyboard-autofill

▲

taikahessu 21 minutes ago | parent | next [-]

Whenever LostPass, I mean LastPass is mentioned, it makes me feel twitchy and reminds me of that time I made a really bad tech decision of using it.

LastPass is not a secure place to store your passwords. Bitwarden is the second worst place. Don't just take my word for it, do your own research.

▲

shantara an hour ago | parent | prev [-]

If you need a tutorial for something that’s supposed to be as simple and transparent as a website authentication, your standard has already failed the usability test.

▲

ylk 20 minutes ago | parent | next [-]

you're misunderstanding: isn't specific to passkeys, this is for changing the password manager(s) used when filling passwords, 2fa codes and passkeys.

since the person I responded to couldn't find it, I linked tutorials. it amounts to opening the Settings app, going to "General" and then "AutoFill & Passwords", so it's also not terribly difficult to find compared to other iOS settings.

you could've at least tried to understand what's being talked about before blindly complaining.

▲

tadfisher an hour ago | parent | prev [-]

This isn't a standards problem, this is an "Apple, Google, and Microsoft made using your own software difficult" problem. They have an interest in making their authenticators the default, and the settings UX on all three platforms makes it unclear that their authenticator is active as well as your own "third-party" authenticator choice.

▲

shantara an hour ago | parent | next [-]

It’s difficult to disentangle one from another, when the companies with the vested financial interest in locking you in are the board members of the consortium creating the standard.

	▲	ethbr1 26 minutes ago \| parent [-]
		Exactly. I'm disinclined to cut Apple, Google, and MS the benefit of doubt for steering a standards committee to spec + real world usage that privileges themselves.

▲

ylk 17 minutes ago | parent | prev [-]

you can see in both the lastpassword and the bitwarden tutorials that the default iOS password manager can be toggled on or off, just like the other options.