-
Notifications
You must be signed in to change notification settings - Fork 61
Reject unmasked client WebSocket frames (RFC 6455 §5.1) #232
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
ianegordon
wants to merge
2
commits into
swhitty:main
from
ianegordon:ian/tvt-1061-reject-unmasked-client-websocket-frames-rfc-6455-51-must
Closed
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm wondering whether
HTTPConnection.swiftis the best place for this validation.Presently, decoding errors from
WSFrameEncoder.decodeFrame(from:)and protocol validation errors from incoming client frames are surfaced through theAsyncThrowingStreamreceived byWSHandler. The handler is responsible for terminating its outgoing server-frame stream and may optionally send a Close frame first.It seems simpler to perform the incoming mask validation in
WSFrameEncoder, perhaps by adding a server-specific decoding method:This requires
decodeFrame(from:)to preserve the decoded mask, as you have in this PR. The client-frame stream could then use something likedecodeClientFrame(from:), and theWSHandlerwill receive the validation error through its existing input stream.MessageFrameWSHandler, which is the higher-level handler I expect most users to use, should already catch this error, emit a protocol-error Close frame, and terminate its outgoing frame stream. This appears to avoid the violation side-channel and task-group coordination currently being added toHTTPConnection.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmmmmmmmmmm..... let me give some thought and check on any related TODOs.
I'll take another pass.