mstdn.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A general-purpose Mastodon server with a 500 character limit. All languages are welcome.

Administered by:

Server stats:

14K
active users

#Passkey

6 posts5 participants0 posts today

Après avoir utilisé #PocketID pendant plusieurs mois avec une installation LXC via les Proxmox Helper Scripts, j'ai remarqué que le service s'exécute en tant que root. J'ai également appris qu'une VM est plus sécurisée qu'un LXC. Cet article vous guidera dans l'installation de PocketID en tant que service non root sur Debian. De plus, un script de mise à niveau est inclus.

#Proxmox #debian #selfhosted #selfhosting #homelab #OIDC #openID #passkey #passkeys

lucasjanin.com/2025/06/02/pock

Last call: c't-Webinar "Passkeys statt Passwörter"

Sichere Logins ohne Passwort sind möglich. Das Webinar zeigt, wie Passkeys funktionieren, wie man sie auf mehreren Geräten nutzt und was bei Problemen hilft.

heise.de/news/Last-call-c-t-We

heise online · Last call: c't-Webinar "Passkeys statt Passwörter"By Anke Brandt

c't-Webinar: Passkeys verstehen und sicher einsetzen

Passkeys bieten eine sichere Alternative zum Passwort. Im Webinar erfahren Sie, wie Passkeys funktionieren, wie man sie einsetzt und worauf man achten muss.

heise.de/news/c-t-Webinar-Pass

heise online · c't-Webinar: Passkeys verstehen und sicher einsetzenBy Anke Brandt

I heard Amazon allowed passkeys now (I don't use Amazon any more, but I've still got my account for my order history) so I decided to check it out.

In reality, one of these passkeys is the default *Android* provider, and the other is a Yubikey. 0 stars for the passkey interface: the data are wrong, I can't tell them apart, and I have no way to rename them even if I could. Must. Do. Better.

I'm really glad I moved everything away from #Google a while ago. Just tried to enable #2FA with some FIDO2 keys and they won't allow it without setting a PIN on them. They're really pushing the #Passkey bullshit hard. Well, no 2FA on Google, then.

Why does Google sometimes show me a QR code to sign in using a #passkey, but other times it lets me sign in with #1Password? Is the 1Password extension the problem?

I will never, ever want to sign in using the terrible QR code passkey workflow. Sadly, when this happens, there seems to be no way to avoid it.

Continued thread

I might have to switch back to BitWarden if for no other reason than to get #PassKey support working across all my different browsers.

Of course KeePassXC support PassKeys but that doesn't help much if your browser can't connect to the locally running KeePassXC database!