this post was submitted on 04 Nov 2023
240 points (94.1% liked)

Technology

33714 readers
267 users here now

This is the official technology community of Lemmy.ml for all news related to creation and use of technology, and to facilitate civil, meaningful discussion around it.


Ask in DM before posting product reviews or ads. All such posts otherwise are subject to removal.


Rules:

1: All Lemmy rules apply

2: Do not post low effort posts

3: NEVER post naziped*gore stuff

4: Always post article URLs or their archived version URLs as sources, NOT screenshots. Help the blind users.

5: personal rants of Big Tech CEOs like Elon Musk are unwelcome (does not include posts about their companies affecting wide range of people)

6: no advertisement posts unless verified as legitimate and non-exploitative/non-consumerist

7: crypto related posts, unless essential, are disallowed

founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] jet@hackertalks.com 20 points 8 months ago* (last edited 8 months ago) (2 children)

The secret key pair of a passkey is never transmitted over the internet. Even if somebody snoops the authentication, they will not be able to reproduce the secret key to login in the future.

Think of it just like SSH public and private keys.

Normal passwords, are typically provided at login time, and get transmitted, relying on HTTPS to keep them secure, if somebody could observe the authentication, they could reproduce the password later.

(Yes someone could hash the password client side and send over the output... But that's extra work and not guaranteed)

[–] towerful@programming.dev 10 points 8 months ago (1 children)

Client side hashing of a password just makes the hashed result the password, as far as security is concerned.
Unless there is some back-and-forth with the server providing a one-time-use salt or something to make each submission of the password unique and only valid once, at which point that might get snooped as well.
Better off relying on client certificates if you are that concerned

[–] linearchaos@lemmy.world 1 points 7 months ago

Passkey's approach is actually relatively close to client side certificates. It's just in a form that is compatible with using a password manager. From the user standpoint once everything supports it properly, logins become relatively transparent and man-in-the-middle is pretty effectively mitigated. The other upside is of course unless you're hosting your own stuff, no one supports client side certificates. This is an opportunity for all the big players to actually push people into better security.

[–] Lem453@lemmy.ca 5 points 8 months ago

Ah, thanks for that explanation. That makes sense. Eliminates a possible attack vector with https