Differences

This shows you the differences between two versions of the page.

--- litespeed_wiki:config:mod_security_faq [2018/10/08 20:34]
Jackson Zhang [Unsupported Variable error]
+++ litespeed_wiki:config:mod_security_faq [2019/06/06 15:34]
qtwrk
@@ Line 1: / Line 1: @@
 ====== Mod Security FAQ for LiteSpeed Web Server ======
+===== Does LSWS Support the "@inspectFile" ? =====
+Yes, but please make sure that when use @inspectFile with 3rd-party scanner, the script returns ''0'' for block , and ''1'' for continue/pass.
+Example code from mod_security [[https://github.com/SpiderLabs/ModSecurity/wiki/Reference-Manual-%28v2.x%29#inspectfile|reference manual]]:
+<code>
+$output = "0 Unable to parse clamscan output [$1]";
+if ($error_message =~ m/: Empty file\.?$/) {
+    $output = "1 empty file";
+}
+elsif ($error_message =~ m/: (.+) ERROR$/) {
+    $output = "0 clamscan: $1";
+}
+elsif ($error_message =~ m/: (.+) FOUND$/) {
+    $output = "0 clamscan: $1";
+}
+elsif ($error_message =~ m/: OK$/) {
+    $output = "1 clamscan: OK";
+}
+</code>
 ===== Does LSWS Support the "Concurrent" Type of Audit Log? =====
@@ Line 6: / Line 29: @@
 A concurrent-mode audit log is only useful for servers like Apache which is process-driven and has multiple processes that may change UID. LiteSpeed is event-driven, and as such, concurrent mode is not needed.
-===== Unsupported Variable error ====
+===== Unsupported Variable Error ====
-Sometime you may see some error like the following:
+Sometimes you may see some errors like the following:
 -10-08 15:51:43.075081  ERROR   [ModSecurity] FILES:import_file "@rx <": Rule not supported.
@@ Line 42: / Line 65: @@
   /etc/apache2/conf.d/modsec_vendor_configs/imunify360_full_litespeed/100_Init_Initialization.conf
-We try to keep LSWS compatible with the latest mod_security 2.5(and above) and gotroot rules. LSWS supports most of these rules and attempts not to miss any really important features/rules used in the real world. We also keep updating support based on our user feedback.  However, because of the complexity and always updating nature of these security rules, it is not possible to be 100% compatible with Apache at any one time.
+We try to keep LSWS compatible with the latest mod_security 2.5(and above) and gotroot rules. LSWS supports most of these rules. We attempt not to miss any really important features/rules used in the real world, and we regularly add support for more features based on our user feedback.  However, because of the complexity and fluctuating nature of these security rules, it is not possible to be 100% compatible with Apache at any one time.
+The above error messages simply mean the given variables are not supported by LSWS yet. The errors can simply be ignored. We periodically review our mod_security engine and frequently add new support. Stay tuned.
+===== Does LSWS Support the "LocationMatch" directive? =====
+When you use ''SecDebugLogLevel'', ''SecAuditLogParts'' or ''SecAuditLog'' within the ''LocationMatch'' directive, you may see the following errors on LSWS:
+  Directive 'SecDebugLogLevel' is not allowed in current context.
+  Directive 'SecAuditLogParts' is not allowed in current context.
+  Directive 'SecAuditLog' is not allowed in current context.
-The above error messages simply mean these variables are not supported by LSWS yet. They can be simply ignored.
+LiteSpeed Web Server //does// support the ''LocationMatch'' context, however the above three directives may not be configured within it. On LSWS, audit log can only be set at the server level, and the debug log level can be set at vhost level. We have no plans to make these directives available at the matching context level, as it would be counterproductive to the optimization applied to the engine.
-We will periodically review our mod_security engine and add new support to it. Stay tuned.