Repository navigation
fix(security): keep attachment credentials out of live output - #705
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
1 participant
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.
Adopt published Core0.315.0 so live-event and answer output removes internal attachment references containing provider media keys or bot credentials. This retains Core0.314.0's protected-state upload and inherited read-only relay fixes.
The earlier MAX release attempt was cancelled before publication so this security fix ships in the same prepared release. Source privacy regressions and SRI-verified registry module checks cover the changed boundary; full consumer release checks remain required. No real credential is used as a fixture.