-
Notifications
You must be signed in to change notification settings - Fork 4.2k
add WebSocket_Security_Cheat_Sheet.md #1780
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
add WebSocket_Security_Cheat_Sheet.md #1780
Conversation
I don't have much data to back it up but I would think that memory(/resource) exhaustion caused by the lack of control flow/backpressure support in many WebSocket implementations may an important security considerations to add in there? |
Thanks for the feedback, @randomstuff - I think I addressed your concerns, let me know if there's anything else. |
Can you kindly submit this as a separate issue? |
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 have some suggestion to add to this, but nothing is wrong and its a great start.
|
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.
Awesome work! Thanks @maheshkukreja
* add WebSocket_Security_Cheat_Sheet.md * address randomstuff's comments
This PR fixes issue #1716.
As a follow up, we'll need to clean up the HTML5 Security Cheat Sheet to remove websocket related text in there.