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

Implement support to the SCRIPT_* variables in libmodsecurity #1017

Closed
zimmerle opened this issue Dec 9, 2015 · 1 comment
Closed

Implement support to the SCRIPT_* variables in libmodsecurity #1017

zimmerle opened this issue Dec 9, 2015 · 1 comment

Comments

@zimmerle
Copy link
Contributor

zimmerle commented Dec 9, 2015

The following variables needs to be implemented inside libModSecurity:

  • SCRIPT_BASENAME
  • SCRIPT_FILENAME
  • SCRIPT_GID
  • SCRIPT_GROUPNAME
  • SCRIPT_MODE
  • SCRIPT_UID
  • SCRIPT_USERNAME

More information about these variables can be found at ModSecurity reference manual: https://github.com/SpiderLabs/ModSecurity/wiki/Reference-Manual

@zimmerle
Copy link
Contributor Author

The set of variables SCRIPTS opens a very interesting discussion. Within v3 and it seamless approach, the rules while executed [should] produce the same response regardless of the server that is hosting the content or server configuration. That is not the case for the set of variables SCRIPTS, where the need of understanding server configuration (path, permission and so on) are needed. I also think that those variables could be replaced for different ones, within representation in the request itself, not on the server configuration. With that said, I am marking this issue as closed.

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

1 participant