-
Notifications
You must be signed in to change notification settings - Fork 11
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
Sanitize username and chat messages using DOMpurify #64
base: master
Are you sure you want to change the base?
Sanitize username and chat messages using DOMpurify #64
Conversation
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.
Looks good to me.
Could you take a look at this? @sachin2912 @s-katte?
sure |
@VaibhavSaini19, I have gone through docs here, and as you can see, they recommend not to use |
Since we are using it to sanitizing the input given by the user instead of a custom template string, it is safe to use that attribute here |
@s-katte, please state if you find #64 (comment) satisfactory, so that we can go ahead and merge this one as well. |
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.
Sure, that is fine by me then.
Although the fields have been sanitized, being a completely client-side code, anyone with a knack of Js knowledge can modify the code and inject malicious script back again.