Repository navigation
Connect public viewers through automatic Spry TLS credentials - #53
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.
Public viewers with direct UDP restricted could play the mix but could not join a useful peer route. Active playback now obtains and renews a unique expiring Spry TLS credential from the independent Archy operator, alongside direct STUN discovery. Pause cancels issuance and renewal; issuer failures preserve HTTPS playback. Existing relay connections retire before credential expiry so new dials use a fresh lease while the HLS player and verified cache continue.
The static bundle and diagnostics contain no relay password or operator root secret. The separately deployed issuer is maintained in forgesworn/archipelago-apps#42, with origin checks, bounded issuance/connections, a private pre-minted credential pool and an isolated TLS listener. Cache tags, integration guidance and LLM discovery text describe the new public route.
Validation: all 244 Node tests pass, including lease validation, coalescing, renewal, cancellation, slow-response expiry and native connection construction with refreshed credentials; site build and staged secret scan pass. Published-origin Chrome CORS and native Spry TLS transferred one hash-verified MiB in each direction without private profiles. Sustained cold-cache 4K contribution, actual long-session transport rotation and physical iPhone acceptance remain separate ongoing checks.