We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
This is related with feature request owasp-modsecurity/ModSecurity-nginx#121
Modsecurity should reopen audit log on these two signals for proper logrotate operation.
As noted at owasp-modsecurity/ModSecurity-nginx#121 (comment), we could leverage a similar approach as described at https://forum.nginx.org/read.php?29,247488,247500#msg-247500 (i.e. use standard nginx API to open some stub-file with ngx_conf_open_file(), add required handler, and use it for detecting USR1 and HUP signals from master process)
But it seems like libModSecurity currently does not have a nice interface to initiate audit/debug log files reopening by connector's request.
There's a PoC on how we could accomplish that on the connector at owasp-modsecurity/ModSecurity-nginx#121 (comment) as a starting point.
The text was updated successfully, but these errors were encountered:
Any news up on that?
Sorry, something went wrong.
zimmerle
victorhora
Successfully merging a pull request may close this issue.
This is related with feature request owasp-modsecurity/ModSecurity-nginx#121
As noted at owasp-modsecurity/ModSecurity-nginx#121 (comment), we could leverage a similar approach as described at https://forum.nginx.org/read.php?29,247488,247500#msg-247500 (i.e. use standard nginx API to open some stub-file with ngx_conf_open_file(), add required handler, and use it for detecting USR1 and HUP signals from master process)
But it seems like libModSecurity currently does not have a nice interface to initiate audit/debug log files reopening by connector's request.
There's a PoC on how we could accomplish that on the connector at owasp-modsecurity/ModSecurity-nginx#121 (comment) as a starting point.
The text was updated successfully, but these errors were encountered: