8000 Add configurable timestamp format to our ftw integration · Issue #953 · coreruleset/coreruleset · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
8000

Add configurable timestamp format to our ftw integration #953

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.

Sign up for GitHub

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

Jump to bottom
Closed
CRS-migration-bot opened this issue May 13, 2020 · 0 comments
Closed

Add configurable timestamp format to our ftw integration #953

CRS-migration-bot opened this issue May 13, 2020 · 0 comments

Comments

@CRS-migration-bot
Copy link

Issue for tracking original pull request created by user dune73 on date 2017-11-09 09:18:01.
Link to original PR: SpiderLabs/owasp-modsecurity-crs#953.

HEAD is: 0652365
BASE is: 5226a30
FTW checks apache error logs to find out if ModSecurity / CRS triggered the right alerts. The matching is performed via timestamp match. First via a regex matching the logfile, then by generating a corresponding timestamp itself and the filtering of the loglines during the time delta.

This PR adds the option to define an alternative log timestamp format via config.py.

It also documents config.py a bit better and adds two additional values that are commented out (and match the reverse timestamp format used in the tutorials).

I just noted that the diff includes a change of the default value for log_location_linux. I am going to revert that immediately via a separate commit.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@CRS-migration-bot
0