Skip to content
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

Run FTW for testing #18

Open
jcchavezs opened this issue Jan 16, 2023 · 3 comments
Open

Run FTW for testing #18

jcchavezs opened this issue Jan 16, 2023 · 3 comments

Comments

@jcchavezs
Copy link
Member

jcchavezs commented Jan 16, 2023

Like every other connector this library should be tested under FTW

@airween
Copy link
Collaborator

airween commented Jan 16, 2023

Just FYI: beside the mentioned test framework we also use go-ftw.

To use either one, it needs to set up a web server (we prefer Apache2).

Furthermore there is a library-tester tool, called ftwrunner, which waits for libcoraza to finish, but it does not need any connector (neither any web server).

Maybe it would be enough to run the tests with this first.

@jcchavezs
Copy link
Member Author

I meant go-ftw actually.

@airween
Copy link
Collaborator

airween commented Jan 16, 2023

As I remember there is only one thing missing from coraza/libcoraza (?): the callback function for the engine.

See ftwrunner's source.

This function passes to the engine, which sends the messages to the connector. For the example, see this snippet.

In case of ModSecurity-nginx, it looks like this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants