Repository navigation
Document transport security for a remote AlignAtt translation server - #469
Merged
Merged
Conversation
The MT protocol sends transcript text and has no authentication, and the guide suggests pointing --alignatt-url at another host. State that the port must not be public and that remote setups should use a private network, an SSH tunnel, or a TLS proxy with a wss:// URL, which the client already verifies. Refs #456.
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.
Summary
Refs #456. The AlignAtt MT protocol carries transcript text and has no authentication, and the guide suggests pointing
--alignatt-urlat a separate host. The guide now says the translation-server port must not be public. For setups across machines, it points to a private network, an SSH tunnel, or a TLS proxy with awss://URL.User impact
Documentation only.
wss://already works: with no explicitsslargument,websockets.sync.client.connectcreates a default TLS context, which verifies the certificate and the hostname. Plainws://to a private host keeps working, so existing LAN deployments are not broken by a URL check.Validation
websockets17.0.1 (websockets.sync.client.connect:ssl = ssl_module.create_default_context()for secure URIs).git diff --check: pass.Checklist
ruff check .. (Markdown only)