reya on Nostr: I'm testing storing the user's private key in the native secure store for Lume v2 ...
I'm testing storing the user's private key in the native secure store for Lume v2 instead of the custom secure store (based on iota stronghold) in v1.
Support:
- Linux (secret-service and kernel key-utils)
- macOS (keychain)
- Windows (credential manager)
But I'm not a security expert, so I'm not sure if it is a good choice or not. I hope I can gather feedback about this change.
I'm also working on NIP-46 (Nostr Connect) to give user more option
#nostrsecurity #nostrdesign 😅
Published at
2023-10-11 07:30:57Event JSON
{
"id": "7372209a4c10559b3d88a571684032566d0cddeae5a16d295c9470c7611368cf",
"pubkey": "126103bfddc8df256b6e0abfd7f3797c80dcc4ea88f7c2f87dd4104220b4d65f",
"created_at": 1697009457,
"kind": 1,
"tags": [
[
"t",
"nostrsecurity"
],
[
"t",
"nostrdesign"
]
],
"content": "I'm testing storing the user's private key in the native secure store for Lume v2 instead of the custom secure store (based on iota stronghold) in v1.\n\nSupport:\n- Linux (secret-service and kernel key-utils)\n- macOS (keychain)\n- Windows (credential manager)\n\nBut I'm not a security expert, so I'm not sure if it is a good choice or not. I hope I can gather feedback about this change. \n\nI'm also working on NIP-46 (Nostr Connect) to give user more option\n\n#nostrsecurity #nostrdesign 😅\n\nhttps://void.cat/d/HdX9XZTd249RArgLmrKtmT.webp",
"sig": "8195fd7505f2c05fe53a0fd2e3ff0c30e0bd1625a54ec4f946842f5ea38ed936814ee59b824f1510d1b663441b9db021d319bf794aefc5d322fd839ddaa56fa3"
}
