Escape incoming message bodies #25
Merged
Conversation
This file contains 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
Purple intereprets incoming message bodies as pseudo HTML, and thus eats <text> - I've not seen it do anything really bad on Pidgin (I can trigger bold but not anything more insecure); not sure other purple frontends. Signed-off-by: Dr. David Alan Gilbert <[email protected]>
|
Looks good. IIRC libpurple does its own sanitisation of received HTML, so this was unlikely to cause anything nasty, but certainly we shouldn't be interpreting Possibly we should be using |
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.
Purple intereprets incoming message bodies as pseudo HTML,
and thus eats - I've not seen it do anything really
bad on Pidgin (I can trigger bold but not anything more insecure);
not sure other purple frontends.
Signed-off-by: Dr. David Alan Gilbert [email protected]