User avatar
🌸 lumi-nhac catbite no_ai antifa 🌱 @lumi@snug.moe
7mo
i love the idea of cryptographic identities being used so you can switch from one server to another in a federated protocol

but you have no guarantee that the original server will delete your private key after you've moved

are there protocols that actually defend against this in some way?
2
0
1
0
User avatar
walnut 🌱 @walnut@thesoftestpaws.net
7mo
@lumi
I'm not sure why you'd need to give the server your private key, account recovery?
1
0
1
0
User avatar
🌸 lumi-nhac catbite no_ai antifa 🌱 @lumi@snug.moe
7mo
@walnut in this case, your identity is a public key and your server is the one that has your private key
1
0
1
0
User avatar
walnut 🌱 @walnut@thesoftestpaws.net
7mo
@lumi
Right, but the only reason I can think of to keep the private identity key on the server and not client side is for account recovery.

There's a proposal for matrix to have portable accounts. Of course, it requires major backwards incompatible changes to the protocol
github.com/Gnuxie/matrix-doc/blob/gnuxie/portable-accounts-in-rooms/proposals/4348-portable-accounts-in-rooms.md
1
0
1
0
User avatar
🌸 lumi-nhac catbite no_ai antifa 🌱 @lumi@snug.moe
7mo
@walnut in the case i am talking about, the client never has the private key, the server does

so we have portable accounts, because the key can be moved

but the origin server could still keep the key, and i'm wondering what countermeasures exist to that being abused
0
0
0
0