owasp-modsecurity / owasp-modsecurity/ModSecurity
Building from (Which) Source. Compilation recipe's instructions using outdate (SpiderLabs) URL's. On Purpose?
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 9.8k
- Forks
- 1.8k
- Avg merge
- 2h 46m
- Merged PRs (30d)
- 1
Description
I am trying to build the Modsecurity Module as a dynamic module for Nginx, on Ubuntu 22.04.
On THIS PAGE https://github.com/owasp-modsecurity/ModSecurity/wiki/Compilation-recipes-for-v3.x#ubuntu-2210 .
Under the "Ubuntu 22.10" --> libModSecurity" section, it shows the following:
$ sudo apt-get install git g++ apt-utils autoconf automake build-essential libcurl4-openssl-dev libgeoip-dev liblmdb-dev libpcre2-dev libtool libxml2-dev libyajl-dev pkgconf zlib1g-dev
$ git clone https://github.com/SpiderLabs/ModSecurity
Shouldn't we be downloading from the new the source (Master) repository from from "Owasp-Modsecurity" like this:
$ sudo apt-get install git g++ apt-utils autoconf automake build-essential libcurl4-openssl-dev libgeoip-dev liblmdb-dev libpcre2-dev libtool libxml2-dev libyajl-dev pkgconf zlib1g-dev
$ git clone https://github.com/owasp-modsecurity/ModSecurity.git
I am trying to build the submodule and libmodsecurity from source and need to know which repository I should be building from. Please let me know. Thanks.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the Ubuntu 22.10 libModSecurity section of the Compilation recipes for v3.x wiki page and compare its SpiderLabs clone URL with the current repository location. Confirm which repository should be used for building libModSecurity and the submodule, then update the documented source URL and verify the instructions remain consistent.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100