nialv7 comments on GitHub auth

[–] nialv7@lemmy.world 23 points 1 year ago (2 children)

Passkey should ask for a password for unlocking. If it doesn't then it's not implemented correctly.

parent

[–] jj4211@lemmy.world 9 points 1 year ago (1 child)

It's client specific and my phone requires whatever can unlock the phone and chrome requires either windows hello or a pin if under linux.

Certain implementations do whatever, and as far as the backend is concerned, there's no way of knowing, unless you want to get into the business of locking down specific vendor keys...

But I say MFA is overrated versus just getting away from generally crappy password factors. Also passkeys are less phish-able than OTP type solutions.

permalink

fedilink

source

parent

hideshow 1 child comment

[–] nialv7@lemmy.world 7 points 1 year ago*

Yes, it's implementation specific, in this case your phone, or your browser is the passkey "device". And as long as it's protected by some form of authentication it's OK (though I would recommend a hardware token over phones/browsers). If it doesn't then you shouldn't be using that "passkey". Yes, there is no way for the website you are authenticating with to know whether your passkey is safe or not, choosing a secure passkey implementation is (unfortunately) the user's job. But it's the same with more traditional 2FAs, e.g. you can store your TOTP secret securely or insecurely, and the website will have no way to know.

permalink

fedilink

source

parent