Repository navigation
Retire hosted relay entry points before credential or network access - #111
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.
Hosted Ormos relay entry points still exposed an unsupported account and networking path. Reject
relayand--configbefore reading configuration, credentials, or contacting a service, and document the local UI as the supported entry point. Preserve protocol inspection and the terminal framing used by the local UI.Validation: subprocess tests verify saved configuration remains unchanged and no service is contacted. Full CLI race tests, lint, six release archive builds and smoke checks, vulnerability and platform checks passed. All 14 browser checks passed; the first browser attempt timed out while a separate engine compilation was using this machine, then passed without changing the timeout.