varjolintu

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?

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.

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

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

The fallback should be fixed in extension version 1.9.0.2.

I'm sure you mean KeePassXC? KeePassX has been dead for years.

It's actually tested with Google. Apple does not work because they have restricted the Passkey creation outside the browser. And there's a list of tested sites in the pull request.

Linux situation is definitely not solved yet, and some sites still ignore Firefox because of missing support. The only reason I mentioned KeePassXC because it's the first free and open source solution that actually supports importing and exporting Passkeys. Even if it's still beta/rc phase.

Every other password manager browser extension injects same kind of scripts to every page (1Password included), because browsers lack an open API for WebAuthn.

KeePassXC's Passkey implementation allows free import/export, and of course Linux is also supported: https://fosstodon.org/@keepassxc/111298602211286675

If you consider KeePassXC to be one of the big players, they (will) support importing and exporting Passkeys.

I agree. An open API in browsers would simplify things a lot.

Every password manager browser extension does a similar injection, including 1Password.

KeePassXC does have auto-fill for browsers. And also Auto-Type which allows you to enter your credentials to _any_ application possible. All this works without any third party plugins.

Magic of course. Talking seriously, it's one more step you'll have to take care of when making extensions for multiple browsers. Using SVG's directly would be much more simple for the devs.

Chromium still doesn't support SVG icons in browser extensions either. Not as extension's own icon or in the browser toolbar. Firefox has supported those for years. Chromium just scales the images to the nearest 16-dip.

There's still nothing about the telemetry in the browser extension? I couldn't find any mention about it in the "Help us improve Proton apps" or from the privacy policy page. The privacy policy mentions "It details the data processing activities specifically related to the creation and activity of your Proton Account when you use Proton Pass." though, but it's a bit unclear.

When looking at the extension's source code, telemetry data is anonymous, but it's always sent to the remote endpoint, and the only way to disable it is from your Proton account, not the extension itself.

From https://proton.me/blog/proton-pass-beta:

"Proton Pass is also one of the first password managers to include a fully integrated two-factor authenticator (2FA) and supports 2FA autofill."

Highly doubt that. There are already multiple password managers with the feature.

FYI: KeePassX had its last release in 10/2016 and the development has been stopped: https://www.keepassx.org/index.html%3Fp=636.html

Browsers should definitely give developers an open API for WebAuthn/Passkeys instead of relying on dirty inject hacks. For now, injecting is the only way to get it to work. Unless you modify the password manager itself to disguise itself as an USB authenticator device.

KeePassXC already has a development branch where WebAuthn is supported in both extension and KeePassXC, so the keys will be stored to your database and can be exported/imported normally. The support needs to be extended and tested for Passkeys also. So yes, controlling your own keys is possible. Browsers just wanted users to use their own walled gardens.

You can also trigger Global Auto-Type from the browser extension with seperate keyboard shortcut (or using context menu), and it handles the URL matching with Auto-Type without any extra extensions.

You can have multiple URL's per entry. However, those only work with the browser extension. Edit entry and go to Browser Integration tab. There's a list of additional URL's.

Greetings from GMT+2.

So.. where I can donate to Firefox _only_?

Please don't use KeePassX. The development stopped already in 2016. Switch to a more active alternative. See: https://www.keepassx.org/index.html%3Fp=636.html