Repository navigation
feat: pair controller accounts over outbound HTTPS - #21
Merged
Merged
Conversation
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.
Link the DC Overview/Watchdog controller through public CryptoLabs code consent and an outbound backend exchange. Require current local administration, CSRF and intentional confirmation, while preserving worker credentials and local update authority.
Persist bounded one-use attempts with process-safe configuration recovery. Retire the unbound legacy callback into a credential-free restart. First-link and same-key confirmation remain supported; different-key replacement is blocked while Watchdog service permission is unknown. Add only the matching nginx routes and preserve exact origin ports.
Validation:
Versions and workflows are unchanged. The central pairing API is a dependency; installed delivery, public signup and paid-service acceptance remain gated through the accepted Fleet channel.