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
This prevents this line from matching and makes the controller return IPv6 not supported by now, sorry.
I just changed the expected length of the ID (from 24 to 27) and I guess you should make the regex less restrictive. Here is the diff I applied locally.
The text was updated successfully, but these errors were encountered:
sbraz
changed the title
Transaction ID can not be parsed from ModSecurity 2.7.3 audit files
Transaction ID can not be parsed from ModSecurity audit files on CentOS/Red Hat
Jun 30, 2016
After a bit of research, it appears that this is caused by a change to Apache mod_unique_id on Red Hat systems. Here are the relevant bug and the patch.
I'm not 100% sure the ID will always have a length of 27, maybe it would be safer to just assume that their size can change and just use \s([a-zA-Z0-9\-\@]+)\sas it would always match.
1)No entry found in the mysql database.
2) Using mlog2waffle daemon
3) while running in debug mode, i see the below error
"IPv6 not supported by now, sorry"
What could be the issue?
My audit files do not match the format expected by waf-fle, they look like:
While they look like this on another system (Ubuntu) with version 2.7.7:
This prevents this line from matching and makes the controller return
IPv6 not supported by now, sorry
.I just changed the expected length of the ID (from 24 to 27) and I guess you should make the regex less restrictive. Here is the diff I applied locally.
The text was updated successfully, but these errors were encountered: