-
Notifications
You must be signed in to change notification settings - Fork 14
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
XML content is not escaped. #7
Comments
Urm, yeah that doesn't seem right. It should at least be easy to fix, I just am not sure how, because I've never been clear about how hxt intends to deal with this. I believe the actual problem is in the implementation of I've now changed this to using |
I'm still not the right person to ask for opinions on HXT. :-) I think it's just not ready, and it's so old and vast it will never be. Thanks for looking into this! Your patch idea reasonable to me. I'll let you know if I can find the time to test it and/or merge our fork with it. |
Not having it here is problematic, as packages depending on it can't pin the repository as the hash of the repository depends on the version of hpack used which can vary from system to system. Stack is actually changing this behaviour soon: https://tech.fpcomplete.com/blog/storing-generated-cabal-files We hit this bug here: wireapp/wire-server#1027 (comment) where now CI isn't reproducible because the cabal file generated on my machine doesn't match the cabal file generated on CI
I just got the following test case to pass over in saml2-web-sso:
Not sure how big of a security issue that is, but it doesn't seem right. I'm wondering if there is some escaping functionality in HXT that is just hard to call in all the right places?
I don't think this'll be trivial to fix. I have worked around this in
saml2-web-sso
in hopefully all the places for now.The text was updated successfully, but these errors were encountered: