[os-OPNWAF] A permanent import path for custom rules is needed #5350
Description
Important notices
Before you add a new report, we ask you kindly to acknowledge the following:
- [ x] I have read the contributing guide lines at https://github.com/opnsense/plugins/blob/master/CONTRIBUTING.md
- [x ] I have searched the existing issues, open and closed, and I'm convinced that mine is new.
- [ x] When the request is meant for an existing plugin, I've added its name to the title.
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
We develop professional applications with fields that allow text to be sent between a secure client and the proxy; this text is recognized as a Unix command (ID 932250), even though it isn’t (example: we had a company with “SH” in its name). In this case, ModSecurity is too strict; we need to allow ARGS input for certain fields using a whitelist (and that is the most restrictive setting we can choose). These fields are accessible only to the logged-in user and controlled with an Endpoint on the application server too.
Describe the solution you'd like
A clear and concise description of what you want to happen.
(e.g. I would like an input field in the /ui/firewall/alias which would add .... to ....)
We need the ability to have a permanent import path for custom rules with the highest possible priority in the httpd includes.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
We create our files in the Includes folder, but these are overwritten with every update of the OPNSense system, so we have to back up and restore the files every time. I think it’s a real challenge for us—and possibly for others as well—to set up and maintain such a workflow.
Additional context
Add any other context or screenshots about the feature request here.