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

ipMatchFromFile does not support comments in v3 #2554

Closed
tomsommer opened this issue Apr 16, 2021 · 11 comments
Closed

ipMatchFromFile does not support comments in v3 #2554

tomsommer opened this issue Apr 16, 2021 · 11 comments
Labels
3.x Related to ModSecurity version 3.x

Comments

@tomsommer
Copy link
Contributor

ipMatchFromFile supported #-comments in v2, this is not possible in v3 and just reports a generic error

@zimmerle
Copy link
Contributor

Hi @tomsommer that is already fixed on v3/master. Yet to be released. For the reference 42a16c7

@zimmerle zimmerle self-assigned this Apr 29, 2021
@zimmerle zimmerle added the 3.x Related to ModSecurity version 3.x label Apr 29, 2021
@tomsommer
Copy link
Contributor Author

tomsommer commented Jul 11, 2022

This is still broken in 3.0.7

Blank lines are ignored, but lines that begin with # still throw errors with ipMatchFromFile

The fix in #1645 only applied to pmFromFile?

@zimmerle

@feanorknd
Copy link

we need comments in the file ;)

@daveram
Copy link

daveram commented Dec 1, 2022

Issues like this are what prevent large enterprises and vendors like most of my clients from moving to mod_security v3

Comments in the file are used to denote which ranges are for what, so others don't have to go looking them up separately or note them elsewhere if we had to put in a rule against specific ranges and what they represent

@martinhsv
Copy link
Contributor

Hi all, thanks for re-raising this.

Per the observation by @tomsommer , this item appears to have been incorrectly closed since the fix for #1645 was for a different operator.

@martinhsv
Copy link
Contributor

If anyone wants to try it out, I have created a pull request for this at #2839 .

I will tentatively plan to merge it within a few days.

@tomsommer
Copy link
Contributor Author

@martinhsv any chance of getting this fix in a release?

@martinhsv
Copy link
Contributor

@tomsommer ,

Since it has already been merged to v3/master, it will be in the coming v3.0.x release by default.

@tomsommer
Copy link
Contributor Author

@martinhsv I meant can we get a release :)

@martinhsv
Copy link
Contributor

Hello @tomsommer ,

There is a v3.0.x release tentatively planned for the near-ish future (let's call it 5-7 weeks).

In the meantime feel free to build from source. (Or are you in a position where the policy at your installation only allows use of official releases?)

@tomsommer
Copy link
Contributor Author

tomsommer commented Feb 21, 2023

@martinhsv built from source and this issue is indeed resolved. Found another issue though (#2877) :)

Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3.x Related to ModSecurity version 3.x
Projects
None yet
Development

No branches or pull requests

5 participants