-
-
Notifications
You must be signed in to change notification settings - Fork 188
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature request] Implement Nostr signer in the Keepassxc browser plugin #2388
Comments
What prevents you for using a custom KPH attribute ( |
That would give your private key to the different Nostr web clients. A nip-07 browser extension allows you to sign Nostr events on web-apps without having to give them your keys https://github.com/aljazceru/awesome-nostr#nip-07-browser-extensions |
I have no previous knowledge about the whole Nostr, but looking at the video here https://github.com/fiatjaf/nos2x I can see that you can enter the public or private key directly to the input field. The extension can already support scenarios like that. Isn't that a viable solution? |
Yes, you can. But isn't recommended to put the private key in the input field of services (web-apps) you don't know if the dev has good intentions or not. That's why there is the NIP-07 proposal of implementation. |
This feels like an alternate universe passkey |
Yeah... looks like it is. LOL. |
Hi,
Nostr is a protocol (Notes and other stuff transmitted by relays) that can be used for building social networks, blogs, reddit-like sites, and so on.
This protocol works using keys (public and private), and there is a NIP (Nostr Implementation Possibilities) that is used to provide a way to sign in to a Nostr platform without giving them the private key.
It would be interesting to see this implemented in Keepassxc instead of using another browser plugin to do it.
NIP-07 description: https://github.com/nostr-protocol/nips/blob/master/07.md
An implementation for Chrome: https://github.com/fiatjaf/nos2x
The text was updated successfully, but these errors were encountered: