-
Notifications
You must be signed in to change notification settings - Fork 292
SecDebugLog does not work. #17
New issue
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
Comments
and it looks like it does not work... I think the rule should block such URLs like https://mysite.com/test |
I see the same issue. The nginx worker process is actually writing debug log lines to stdout. Additionally, the test executables provided with libmodsecurity also write to stdout even when SecDebugLog is configured, though I see several |
Hi @p0pr0ck5, I am looking into this bug at this very moment. I will have more information in a few minutes. |
The DebugLog implementation was modified to use shared memory to keep the information about the opened files and file handles. The modification was necessary to avoid race-conditions. This commit also closes the issue owasp-modsecurity/ModSecurity-nginx#17
Hi @p0pr0ck5 and @olekstumedia, Took some time but the problem should be fixed by: owasp-modsecurity/ModSecurity@678a97d |
Im facing similar issue, Not able to find anything from SecDebugLog in the defined location. 0 lines in the file. Is this issue fixed ? if so whats the solution ? @olekstumedia @zimmerle |
Has this in my site vhost config file for Nginx. By some reason debug log does not work ... although audit one works. What could be the reason? how to troubleshoot such issues(( It looks like a bug
The text was updated successfully, but these errors were encountered: