-
Notifications
You must be signed in to change notification settings - Fork 17
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
Current limitations of the ModSecurity v3/dev/wasm-experimental branch? #34
Comments
Hi, I have tested the commands, it works. Can you attach your steps or errors. |
I removed the "--without-libxml" switch and changed the file https://github.com/intel/modsecurity-wasm-filter/blob/main/wasmplugin/Dockerfile to also install libxml2
|
Hi, is it necessary to use libxml? we remove libxml because we havn't build the WASM LIB for libxml. |
Also, what features or use cases might be impacted by the code changes in the ModSecurity V3 wasm-experimental branch? owasp-modsecurity/ModSecurity@v3/master...v3/dev/wasm-experimental |
I see. Without the libxml, conditions on XML variables won't evaluate properly, I assume. |
Hi @dspeg, just like @leyao-daily pointed out, all the |
The changes mostly remove everything related to file system, network and other system calls not yet supported by Wasm such as the generation of random transaction IDs or exception handling. It mainly impacts the possibility of providing rules and There is still also ongoing work that has to be done in order to improve the stability of the filter (E.g. owasp-modsecurity/ModSecurity#2783) and reduce unexpected behaviours that the users may face (Currently, if the filter stops working, the Envoy filter chain breaks, and all the requests return a |
Thanks @leyao-daily and @M4tteoP for the detailed info! |
"The changes mostly remove everything related to file system ..." Then the Mod Security operator "pmFromFile" won't work? Are there additional workarounds besides changing "pmFromFile" to "pm" to make it "inline"? |
To the best of my knowledge:
It will not, because it is looking for its related
Currently, I don't think so. Speaking about
Would be really nice. it is something that coraza-proxy-wasm is doing with one line thanks to Golang, but C++ side I'm not aware of a solution like this one. |
Thank you @M4tteoP for the in-depth explanation. |
You are welcome @dspeg! Feel free to provide any feedback about the custom separator, even just for showing interest from the community :) |
What are the limitations from the below changes to the ModSecurity V3 branch?
owasp-modsecurity/ModSecurity@v3/master...v3/dev/wasm-experimental
Did we choose the ModSecurity build options mainly to reduce the wasm binary size or to make the build successful?
For examples:
--without-libxml: I tried removing this switch, and this caused build errors in libxml source code.
--without-geoip: Any comments?
The text was updated successfully, but these errors were encountered: