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

Wrong Documentation SecUploadKeepFiles #1205

Open
security-database opened this issue Nov 7, 2024 · 10 comments
Open

Wrong Documentation SecUploadKeepFiles #1205

security-database opened this issue Nov 7, 2024 · 10 comments

Comments

@security-database
Copy link

Description

Trying to play with coraza-spoa it seem that the SecUploadKeepFiles RevelentOnly doc is wrong

Expected result

SecUploadKeepFiles RevelentOnly (By the doc)

Actual result

RevelentOnly On/Off (by the code)

Capture d’écran 2024-11-07 à 15 49 53

Thanks for your work

@security-database
Copy link
Author

In addition, same on coraza.io website
Capture d’écran 2024-11-07 à 15 56 39

@fzipi
Copy link
Member

fzipi commented Nov 8, 2024

Hey @security-database! Thanks for creating this issue! Are you up for a PR?

@fzipi
Copy link
Member

fzipi commented Nov 22, 2024

@security-database ping.

@security-database
Copy link
Author

security-database commented Nov 22, 2024

@fzipi i think i can do a PR ;) But i don't know what is good / wrong. Is the Doc good but Code wrong ? Or reverse ? Because if you stick to modsecurity, code is wrong - and for that, i cannot do a PR

To be clear, i cannot write and submit code change, but can test changes.

@fzipi
Copy link
Member

fzipi commented Nov 22, 2024

That is definitely a bad copy and paste. The modsecurity code should be the good behavior and docs.

@fzipi
Copy link
Member

fzipi commented Nov 22, 2024

So RelevantOnly is a thing here. Then the code must be fixed, and docs are good.

@security-database
Copy link
Author

So RelevantOnly is a thing here. Then the code must be fixed, and docs are good.

But as you can see,

Note : RelevantOnly is not yet supported on libModSecurity

So it's not implemented every time. If so, you could just for the moment update the doc and plan to add it on later version ?

@fzipi
Copy link
Member

fzipi commented Nov 22, 2024

Yes, updating the doc to match reality would be the first thing to do.

Because this might have different outputs depending on the middleware, I don't think that at the Coraza layer we can make a decision. That's probably why in libModSecurity is not implemented.

@security-database
Copy link
Author

Agree

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

No branches or pull requests

2 participants