Repository navigation
docs(guide): one pairing is enough; keep keys out of the conversation (cli 4.0.1) - #42
Merged
Merged
Conversation
Coordinators the agent runs may share its Home Key. The agent never asks for a second pairing code per machine and never explains keys, tokens or pairing internals to the owner. CLI 4.0.1.
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
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.
From Mathieu's test: the agent told him the Pi shared its key and offered a second pairing code. The owner neither understands nor needs that. Coordinators may share the agent's Home Key; keys and pairing internals stay out of the conversation.