Ya really what you want is your passwords saved in an encrypted vault that you can copy from device to device for backup. If passkeys are really one per device and you have have 100 passkeys from 100 different services, and moving to a new device requires accessing each of those 100 services to create a new passkey for the new device, that sounds terrible

> If passkeys are really one per device and you have have 100 passkeys from 100 different services, and moving to a new device requires accessing each of those 100 services ....

I'm typing this on my Firefox remote app. Everything is cached in it. It runs in a VM at home.

I suppose I am simulating having just one device.

Everyone else: don't do this

Why not? It actually sounds like the best way to use passkeys and still have control over them.

I've been super happy with it. My logins are always with me but they never leave the house.

> It actually sounds like the best way to use passkeys and still have control over them.

I belatedly recall that I tried to setup a Google passkey in a VM and was rebuffed. Google depends on Windows Hello for passkey presentation prompts - and Hello is disabled in an RDP session (ostensibly because facial rec won't be needed).

I poked at the problem for a while and couldn't find a workaround.

It's a safe, simple and secure config. I understand that's not for everyone.

It's simple and convenient, it may or may not be secure, it is not safe, it's fragile. I understand avoiding unnecessary single points of failure is not for everyone.

> it may or may not be secure

It is secure.

> it is not safe,

This is incorrect.

> it's fragile

This is incorrect. Many thousands of sessions over most of a decade all testify to to it's robustness and reliability.

> I understand avoiding unnecessary single points of failure is not for everyone.

That's an interesting segue.