Item — HN Reader

> The WebAuthn thing could, in theory, make the browser remember your key so you don't have to pin every time you use it, but that only happens when Apple, Google and others implement this proposed standard. Right now, no browser can call it. Not Chrome, not Safari, not anything.

Wikipedia says that "WebAuthn is supported by Google Chrome, Mozilla Firefox, Microsoft Edge, Apple Safari[13] and Opera.[32]"

https://en.wikipedia.org/wiki/WebAuthn

Here's a Chrome link published back in 2018

https://developer.chrome.com/docs/identity/webauthn

Here's a Chrome DevTools article on their support for WebAuthn

https://developer.chrome.com/docs/devtools/webauthn

Perhaps you should check your notes?.If you know something that everyone around you doesn't, please update wikipedia's article.

2 comments

Perhaps you should look at the announcement. Of course webauthin is in the browsers. They didn’t announced that they now support webauthn??? I said the webauthn THING because it’s an addition to that functionality!

A 2018 page announcing the base API, and a devtool page about the virtual authenticator debugger is not relevant to this new extensions.

The thing that’s an unshipped proposal is the sign extension.

So my point stands, nothing new and useful in this at all and nothing they announced is usable for anybody today.

Or am I mistaken? What new thing will you, or anybody, do with this 5.8 announcement?

> Perhaps you should look at the announcement. Of course webauthin is in the browsers.

Yes. You sound really confused right now. Perhaps you should take a step back and check your notes.

> So my point stands

I don't think it does. It's quite obvious your claim about webauthm contrasts with reality. If you take the offer to check your notes, you can start here.

https://developer.mozilla.org/en-US/docs/Web/API/Web_Authent...

But something tells me no evidence in the world will sway your beliefs.

What does the word “pin” mean in this sentence? Looks like a typo.

It was misleading by me also. As mentioned, terrible work day yesterday, so I was writing angrily. Ironic that I accuse the security people of being bad at explaining, then turn around and explain stuff badly myself...

Ill TRY to make it up by explaining it as i understand this.

This is not adding the pin functionality, I was just focusing on the flow that happens when you get the Fido2 challenge flow on a webpage. That functionality is already there. Thee new thing is the 5.8 ads support for a second roundtrip/flow for signing stuff in browsers.

Right now, a YubiKey does only one thing in browser: signing a "login challenge string" from the webpage (FIDO2 flow). This is just slightly simplified: (random number + domain + some other shit). Fingerprint that string and return that cryptographically signed result to the site, as proof that "Only I could have signed this login challenge."

Right now, that's the only supported back-and-forth flow for signing anything with a YubiKey vs. a browser.

The new thing is that YubiKey wants a second flow, where the browser sends a request to sign any arbitrary text. So the page contains a contract, converts that to a fingerprint, the browser sends the fingerprint to YubiKey, YubiKey cryptographically signs this, and you can post the resultant string anywhere (public key cryptography magic), and that proves that the person holds that hardware key signed that exact input string (the contract).

So if/when Chrome, Safari, Firefox, and more accept this standard, you could click a button below a contract on a webpage, and the back-and-forth dance with the YubiKey would result in a string below that contract being cryptographic proof that the exact contract above is signed by the person holding one specific key.

Notice the lack of any AI-related shit in this functionality, yet the article reads 5.8 is a revolution for security in "the AI era"

It means entering a personal identification number (PIN) as an authentication step.