naxsi | high performance , low rules maintenance WAF | Firewall library

 by   nbs-system C Version: 1.3 License: GPL-3.0

kandi X-RAY | naxsi Summary

kandi X-RAY | naxsi Summary

naxsi is a C library typically used in Security, Firewall, Nginx applications. naxsi has no bugs, it has a Strong Copyleft License and it has medium support. However naxsi has 1 vulnerabilities. You can download it from GitHub.

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.
Support
    Quality
      Security
        License
          Reuse

            kandi-support Support

              naxsi has a medium active ecosystem.
              It has 4286 star(s) with 597 fork(s). There are 228 watchers for this library.
              OutlinedDot
              It had no major release in the last 12 months.
              There are 71 open issues and 409 have been closed. On average issues are closed in 71 days. There are 3 open pull requests and 0 closed requests.
              It has a neutral sentiment in the developer community.
              The latest version of naxsi is 1.3

            kandi-Quality Quality

              naxsi has 0 bugs and 0 code smells.

            kandi-Security Security

              naxsi has 1 vulnerability issues reported (0 critical, 0 high, 0 medium, 1 low).
              naxsi code analysis shows 0 unresolved vulnerabilities.
              There are 0 security hotspots that need review.

            kandi-License License

              naxsi is licensed under the GPL-3.0 License. This license is Strong Copyleft.
              Strong Copyleft licenses enforce sharing, and you can use them when creating open source projects.

            kandi-Reuse Reuse

              naxsi releases are available to install and integrate.
              Installation instructions, examples and code snippets are available.

            Top functions reviewed by kandi - BETA

            kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
            Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of naxsi
            Get all kandi verified functions for this library.

            naxsi Key Features

            No Key Features are available at this moment for naxsi.

            naxsi Examples and Code Snippets

            No Code Snippets are available at this moment for naxsi.

            Community Discussions

            QUESTION

            All Laravel routes are not found (404 error) on https://proclubs.app/login
            Asked 2021-Oct-02 at 20:26

            I have deployed my Laravel app to the following url proclubs.app - this is a domain from Google domains that requires an SSL certificate (the SSL has been setup using Certbot).

            I have setup the Laravel Breeze package for authentication (e.g register/login functionality) and this all works fine when testing locally, now I have pushed this to a remote URL none of the routes don't work, and I just get a 404 Not Found message. I have ran the php artisan route:list and can see all the expected routes are there. I am 99% certain I have made a mistake with the nginx server block - I have used the default one that digitalocean provide in etc/nginx/sites-available and edited it accordingly, but not sure what is incorrect for me to get these 404 errors, can anyone suggest what I have done wrong?

            ...

            ANSWER

            Answered 2021-Oct-02 at 20:26

            If you get 404, probably requested path wrong. I checked your nginx configurations and I see you have 2 servers, for http (first server) and https (second server) requests.

            When you enter the url /login path it means that you want to go login folder. But in laravel it is special request.

            So your mistake is in the second server (https) your request find a folder, not a special request. You must change your location option with the first server location option.

            Source https://stackoverflow.com/questions/69418949

            QUESTION

            SSL Certificate Working for Domain but not Specific Port
            Asked 2020-Mar-02 at 05:09

            I have a domain sub.example.com that is configured and fully functioning on an Ubuntu server. I used Certbot to configure the domain with HTTPS, however I also have APIs configured to be accessed on a specific port of that domain, say 2500. When I access example.com, I see the lock that says the site is secure, however whenever I go to example.com:2500/api/someAPI, the API returns the appropriate result, but without the site being secure. Because the main site is secure, while the API access location isn't, I am unable to make API calls accordingly, resulting in net::ERR_SSL_PROTOCOL_ERROR.

            Stack:

            1. VPS: Amazon EC2
            2. SSL Cert Provider: Let's Encrypt (through Certbot)
            3. Server: Node.js (Express)
            4. WebApp: React
            5. Web Server: nginx

            I was able to get it working using the same exact technologies on another VPS (DigitalOcean) and domain some time ago, but I don't believe I ever ran into this issue.

            nginx.conf:

            ...

            ANSWER

            Answered 2020-Feb-28 at 22:44

            By default, no other port than port 443 uses the secure connection. However, if you specify to do so (such as using https://example.com:2500) it should connect securely. If you want it to do this automatically, you need to configure it in the web server application settings. If you know what application is used to host the server (ex. apache) and if you have access to edit the configuration files, you should be able to configure this.

            Edit: Sorry, I did not originally see you tagged the question as using nginx. I have not done this specifically before using nginx, but I found this tutorial that explains the process. Inside of /etc/nginx/sites-available/example.com, you should be able to change "listen 443 ssl;" to "listen 443, 2500 ssl;" in order to listen on multiple ports. In addition, you would also add return 301 https://$host$request_uri;in order to redirect connections to an https secure connection (see https://serversforhackers.com/c/redirect-http-to-https-nginx).

            I hope this helps!

            Source https://stackoverflow.com/questions/60460045

            Community Discussions, Code Snippets contain sources that include Stack Exchange Network

            Vulnerabilities

            No vulnerabilities reported

            Install naxsi

            The documentation
            Some rules for mainstream software
            The nxapi/nxtool to generate rules

            Support

            For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .
            Find more information at:

            Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items

            Find more libraries
            CLONE
          • HTTPS

            https://github.com/nbs-system/naxsi.git

          • CLI

            gh repo clone nbs-system/naxsi

          • sshUrl

            git@github.com:nbs-system/naxsi.git

          • Stay Updated

            Subscribe to our newsletter for trending solutions and developer bootcamps

            Agree to Sign up and Terms & Conditions

            Share this Page

            share link

            Explore Related Topics

            Consider Popular Firewall Libraries

            opensnitch

            by evilsocket

            fail2ban

            by fail2ban

            TheFatRat

            by screetsec

            TheFatRat

            by Screetsec

            ModSecurity

            by SpiderLabs

            Try Top Libraries by nbs-system

            php-malware-finder

            by nbs-systemPHP

            mapster

            by nbs-systemJavaScript

            nxtool-ng

            by nbs-systemPython

            snuffleupagus

            by nbs-systemC

            spike

            by nbs-systemPython