Thank you for your recent Tweet regarding cxs and ModSecurity v2.9.
I have tried to edit /usr/local/apache/conf/modsec2.user.conf
As detailed in your blog post:
http://blog.configserver.com/?p=2522
However I see currently no mention of CXS in the configuration file:
"and add the line above after the cxs ModSecurity rule and then restart httpd."
Have I missed an important change I should have made when installing CXS in the first place, some years ago?
Thank you!
cxs and ModSecurity v2.9 Tweet
Re: cxs and ModSecurity v2.9 Tweet
It sounds like cxs scanning using modsecurity was never enabled on your server. It is not necessarily a requirement, especially if you have cxswatch running. However, if you want to use cxs scanning with modsecurity, the easiest way to add it is to use our new cPanel modsecurity vendor as per this blog post:
http://blog.configserver.com/?p=2524
http://blog.configserver.com/?p=2524
Re: cxs and ModSecurity v2.9 Tweet
Ah OK. Thank you.
So if I use your vendor rules, do I not need to worry about the setting change for cxs/modsec 2.9 compatibility at all?
So if I use your vendor rules, do I not need to worry about the setting change for cxs/modsec 2.9 compatibility at all?
Re: cxs and ModSecurity v2.9 Tweet
ie. I have not set this line anywhere:
SecUploadKeepFiles RelevantOnly
Should I?
TY!!
SecUploadKeepFiles RelevantOnly
Should I?
TY!!
Re: cxs and ModSecurity v2.9 Tweet
No, it will add that line automatically so you do not need to worry about it.
Re: cxs and ModSecurity v2.9 Tweet
Brill. TY.