Hacker Newsnew | past | comments | ask | show | jobs | submit | varjolintu's commentslogin

Doing ukemi to save himself. This is just the first step of the practice. Uke (receiver) co-operates in a way that tori can practice the thing being taught. Only after that things start to change: uke changes something, tries to evade, resists etc. However, this phase is rarely shown in demonstrations. Even more rare if you see the step(s) after that.


Yes. This is mandatory for all browser extensions. There's no API behind a separate permission, even if would be the best way to handle this.


Actually, if you export your vault as JSON, the passkeys are there in plain-text.


I'm curious to know what this "model" actually means. A real-time AI monitoring for conversations?


This infrastructure is already implemented

https://support.discord.com/hc/en-us/articles/12926016807575...


FYI: If you export your Bitwarden vault as plain JSON, passkeys are included in plain-text too. So, it works similar to KeePassXC.


KeePassX is long dead, and it's not with "key" but with "kee" -> KeePassXC. Thank you :)


ようこそ 日本一のモグラえき 土合へ Translates to something like: "Welcome to Doai, Japan's number one mole station (mogura-eki)".


The worst thing about passkeys is how browser extensions must handle them: using JavaScript injections to the web page. Of course this means _any_ browser extension could do the same and be the man-in-the-middle inspecting the passkey creation and authentication. I'd be glad to have some kind of standard API behind a proper permission for handling passkeys.


The only thing that they should be able to intercept there, though, would be the specific passkey for the page you are authenticating with. With the specific challenge that was included, even. Such that it is not exportable to somewhere else for them to authenticate as you.

Sure, it sucks that anything is interceptable. But this is still an improvement over the status quo.


According to this list majority of the clients are out of spec: https://passkeys.dev/docs/reference/known-issues/


The list has been filtered to include only non-compliant clients:

“The following list of passkey providers have not implemented User Verification in a spec-compliant manner.”


A few medical projects (one still being active). And KeePassXC.


Thanks for your work! I use it everyday and recommend it to everyone who has an interest in better password management.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: