fix: persist participant session secret after password verification#35
Merged
fix: persist participant session secret after password verification#35
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.
Description
This bug fix ensures that participants in a private room can correctly decrypt and read the host’s chat messages after password verification.
Previously, the participant-side session secret was not persisted after verification, which caused encrypted chat payloads to be uninterpretable.
By saving the verified participant password into the session secret state, the participant flow now keeps the required encryption context for chat decryption.
Type of Change
Related Issues
Peers cannot interpret the host’s chat in a private room. #30
Changes Made
Checklist