You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
8. When done, the binaries, lib and pdb files should appear under:
93
+
- c:\work\ModSecurity\iis\release\x86 (32-bit)
94
+
- c:\work\ModSecurity\iis\release\amd64 (64-bit)
95
+
96
+
* At this point, if you have a previous installation of ModSecurity and
97
+
would like to test, you can manually place:
98
+
- x86 files to "C:\Windows\SysWOW64\inetsrv"
99
+
- x64 files to "C:\Windows\System32\inetsrv"
100
+
101
+
9. If all went well, you can build the MSI installer by running:
102
+
build_msi.bat
103
+
104
+
The MSI will be created in the release folder.
105
+
106
+
--------------------------------------
107
+
108
+
MSI Installer Features:
109
+
110
+
* Automatically places files to the correct system folders
111
+
* Configures the ModSecurity IIS native module for both 32-bit and 64-bit
112
+
* Registers the module with IIS application configuration
113
+
* Checks for required Visual C++ 2019 Redistributables
114
+
* Provides clear error messages with download links if prerequisites are missing
115
+
* Supports both x86 and x64 architectures
116
+
* Allows selective installation of 32-bit and/or 64-bit modules
38
117
39
118
--------------------------------------
40
119
41
-
1. Create working directory (e.g. c:\work) and drop the latest clone from ModSecurity's 2.x Github (https://github.com/owasp-modsecurity/ModSecurity/archive/v2/master.zip)
42
-
2. Make sure the prerequisites mentioned above are all set
43
-
3. If you haven't download the dependency files before, uncomment the "@call download_files.bat" line on build_dependencies.bat to have them downloaded prior
44
-
4. Open a command prompt (cmd.exe) and head to the "iis" folder inside ModSecurity tree working directory (e.g. cd c:\work\ModSecurity\iis)
45
-
5. If you need to modify anything (e.g. paths, versions etc), carefully edit the batch files.
46
-
6. Run build_release.bat
47
-
7. When done, the binaries, lib and pdb files should appear under c:\work\ModSecurity\iis\release\x86 (32-bit) and c:\work\ModSecurity\iis\release\amd64 (64-bit)
48
-
* At this point, if you had a previous installation of ModSecurity and would like to test you can place the x86 files to "C:\Windows\SysWOW64\inetsrv" and x64 files to "C:\Windows\System32\inetsrv"
120
+
Troubleshooting:
121
+
122
+
* If the installer fails with missing DLL errors, ensure the VC++ 2019
123
+
Redistributables are installed (see Runtime Prerequisites above)
49
124
50
-
8. If all went well, you can build the MSI installer by running the build_msi.bat script.
125
+
* Use the included list_dependencies.bat script in the wix folder to check:
126
+
- VC++ 2019 Redistributable installation status
127
+
- ModSecurity DLL dependencies
128
+
- Missing libraries
51
129
52
-
* The built installable package places the files to the correct folders, automatically configures the ModSecurity IIS native module and configures web.config to enable ModSecurity for all IIS sites.
0 commit comments