The key lives in Notary, and only Notary can reach it - #26
Merged
Conversation
Two pages described a keyholder that Plaza reached "over authenticated loopback". That was true of a shared credential in a file. It is not how it works now, and the difference is the whole point: Plaza starts Notary as its own process and they talk over a channel with no shared file, no fixed port, and no name for anything else to find. The signer page also said the daemon speaks NIP-46 over relays, which is one of the two things it can be. The other is the private keyholder of a single app, and a second daemon cannot open a key that is already open.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Two pages described a keyholder Plaza reached "over authenticated loopback". That was true of a shared credential in a file, and is not how it works now.
Plaza starts Notary as its own process, and they talk over a channel with no shared file, no fixed port, and no name for anything else to find. Holding the channel is what proves who is asking, so there is nothing for another app to read or guess.
The signer page also described the daemon as speaking NIP-46 over relays, which is one of the two things it can be. The other is the private keyholder of a single app that ships it, and one key has one keyholder: a second daemon cannot open a key that is already open.