muffinbi on Nostr: There's something that worried me about having only a private key to login at #nostr ...
There's something that worried me about having only a private key to login at #nostr and not having a way to recover from a leak or invasion. I mean, how can we feel safe if we know that a potential leak of our key will permanent steal our content forever? There's no password change /key change. Today we have several apps that we can use with this protocol plus web browser apps, several browser vendors, extensions, browsers with less security, etc... The ways you can loose your key to an hacker are far way more and faster, than the ways users can learn how to avoid them.
Am I missing something here? Is there a way to associate account to a new private key if it had been compromised?
What are the good practices to avoid this preoccupation?
Published at
2024-01-25 18:51:05Event JSON
{
"id": "6dfbc089cde9abd7022855fd6d62fc1f7256064ac35935fed4372c6f0914cf7b",
"pubkey": "c43951fef90898d1eedfdae6e1b9bf66c3e62dc00d9a9b170bf10f92234fd025",
"created_at": 1706208665,
"kind": 1,
"tags": [
[
"t",
"nostr"
]
],
"content": "There's something that worried me about having only a private key to login at #nostr and not having a way to recover from a leak or invasion. I mean, how can we feel safe if we know that a potential leak of our key will permanent steal our content forever? There's no password change /key change. Today we have several apps that we can use with this protocol plus web browser apps, several browser vendors, extensions, browsers with less security, etc... The ways you can loose your key to an hacker are far way more and faster, than the ways users can learn how to avoid them.\n\nAm I missing something here? Is there a way to associate account to a new private key if it had been compromised?\n\n\nWhat are the good practices to avoid this preoccupation?",
"sig": "2fe67578b906876c57893eaa04dc412f2f0d69d3f7559d6690586b8d48372014d93f6bec3dd097f7f64fc7a8289e65abe853f4594e2fdb0d43f3e9ca4a4d3c90"
}