Re:Passkey Implementation: Misconceptions, pitfalls and unkn...
by p0seidon on Friday May 03, 2024 @05:50AM
(#40245877)
Agree, but I think in a B2C context, you need convenience first; then security can follow.
Re:Passkey Implementation: Misconceptions, pitfalls and unkn...
by bayindirh on Friday May 03, 2024 @07:45AM
(#40246549)
I think it depends. Banking, primary e-mails, etc. are extremely important systems today, and they should bias towards security. Other platforms where we talk can take a more balanced approach, and more casual sites can lean towards convenience, if you ask me.
Re:Passkey Implementation: Misconceptions, pitfalls and unkn...
by joncrocks on Friday May 03, 2024 @11:19AM
(#40248687)
Indeed, the problem with lots of fallbacks is that they can invalidate user's requests for higher security. Security can sometimes end up being only as strong as the weakest link.
Make the fallback too lax and you might as well not bother with 2FA/Passkeys at all.
I don't think that we should target MIL-xxx standards for daily use, but my security is comparably important to me as military's missile codes are important to them.
So, I don't want my passkey-based services to have a security theater in the name of convenience. There should be some friction to force a baseline security.