Seems like this bug is fixed. # apt install libnginx-mod-http-modsecurity --default-release bookworm Reading package lists... Done Building dependency tree... Done Reading state information... Done The following NEW packages will be installed: libnginx-mod-http-modsecurity 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 25.4 kB of archives. After this operation, 196 kB of additional disk space will be used. Get:1 http://ftp.hu.debian.org/debian bookworm/main amd64 libnginx-mod-http-modsecurity amd64 1.0.3-1+b2 [25.4 kB] Fetched 25.4 kB in 0s (331 kB/s) Selecting previously unselected package libnginx-mod-http-modsecurity. (Reading database ... 57140 files and directories currently installed.) Preparing to unpack .../libnginx-mod-http-modsecurity_1.0.3-1+b2_amd64.deb ... Unpacking libnginx-mod-http-modsecurity (1.0.3-1+b2) ... Setting up libnginx-mod-http-modsecurity (1.0.3-1+b2) ... Processing triggers for nginx (1.22.1-9) ... Triggering nginx reload ...
Jul 29 14:11:10 debian12 systemd[1]: Starting nginx.service - A high performance web server and a reverse proxy server... Jul 29 14:11:10 debian12 nginx[1600]: 2023/07/29 14:11:10 [notice] 1600#1600: ModSecurity-nginx v1.0.3 (rules loaded inline/local/remote: 0/921/0) Can we close this issue? a. On Sat, Jul 15, 2023 at 2:51 PM Tobias Frost <t...@debian.org> wrote: > Control: tags -1 pending > Conrtol: block -1 by 1040799 > > This bug has been fixed in unstable with the binNMU 1.0.3-1b3, see #1040858 > > It is also scheduled to be fixed in the next stable-point-release, see > #1040799 > > > -- > tobi >
