summaryrefslogtreecommitdiffstats
path: root/package/nginx-naxsi/Config.in
diff options
context:
space:
mode:
Diffstat (limited to 'package/nginx-naxsi/Config.in')
-rw-r--r--package/nginx-naxsi/Config.in26
1 files changed, 26 insertions, 0 deletions
diff --git a/package/nginx-naxsi/Config.in b/package/nginx-naxsi/Config.in
new file mode 100644
index 0000000000..2f7c2da2a9
--- /dev/null
+++ b/package/nginx-naxsi/Config.in
@@ -0,0 +1,26 @@
+config BR2_PACKAGE_NGINX_NAXSI
+ bool "nginx-naxsi"
+ help
+ NAXSI means Nginx Anti XSS & SQL Injection.
+
+ Technically, it is a third party nginx module, available as
+ a package for many UNIX-like platforms. This module, by
+ default, reads a small subset of simple (and readable) rules
+ containing 99% of known patterns involved in website
+ vulnerabilities. For example, <, | or drop are not supposed
+ to be part of a URI.
+
+ Being very simple, those patterns may match legitimate
+ queries, it is the Naxsi's administrator duty to add
+ specific rules that will whitelist legitimate
+ behaviours. The administrator can either add whitelists
+ manually by analyzing nginx's error log, or (recommended)
+ start the project with an intensive auto-learning phase that
+ will automatically generate whitelisting rules regarding a
+ website's behaviour.
+
+ In short, Naxsi behaves like a DROP-by-default firewall, the
+ only task is to add required ACCEPT rules for the target
+ website to work properly.
+
+ https://github.com/nbs-system/naxsi
OpenPOWER on IntegriCloud