feat: add secure platform publish gate - #40
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.
Summary
publishQueryReffor signed RTMP publish queries while keeping credentials out of endpoint URLs and logsaimedia publish-checkplus stablePublishRejected / Commandclassificationtools/platform.ps1gate for YouTube, Twitch, Tencent Cloud, Alibaba Cloud, and custom endpointsVerification
cargo test --locked -p aimedia-rtmp publish_query_reference_is_transmitted_without_entering_the_endpointcargo test --locked -p aimedia-rtmp publisher_classifies_a_rejected_publish_command_without_peer_detailscargo check --locked -p aimedia-core -p aimedia-rtmpcargo check --offline --locked -p aimediatools/platform.ps1External endpoint status
This PR does not claim platform compatibility. In the current network, YouTube and Twitch ingest names resolve to the local proxy range
198.18.0.0/15and both aimedia and FFmpeg fail during RTMP handshake. Those attempts are documented as failed diagnostics, not as V3-03F3 completion. No real stream key was stored or printed.apps/remains untracked and is not part of this PR.