-
-
Notifications
You must be signed in to change notification settings - Fork 304
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
Increased modsecurity bodynofileslimit so larger files can be synced #993
Conversation
Minor note: I tried testing my PR with
but it looks like it's not considered a branch by github. Not sure if there's another way to test it through the ncp-update process. I 'll look into it when I can. |
many thanks for this. I can merge it to |
6c62d01
to
c1e1b65
Compare
Signed-off-by: nachoparker <[email protected]>
…from desktop client. Signed-off-by: Nikolaos Perrakis <[email protected]>
Signed-off-by: Nikolaos Perrakis <[email protected]>
Refactored the code per to your suggestions and re applied commits on top of current devel branch. |
looks good, thanks. I merged it into |
…993) Signed-off-by: Nikolaos Perrakis <[email protected]> Signed-off-by: nachoparker <[email protected]>
@nachoparker Tested PR with |
great, many thanks!! |
…993) Signed-off-by: Nikolaos Perrakis <[email protected]> Signed-off-by: nachoparker <[email protected]>
…993) Signed-off-by: Nikolaos Perrakis <[email protected]> Signed-off-by: nachoparker <[email protected]>
Temporary(?) fix to #959
Needs testing. I added functionality in
update.sh
to update the config for people who already have modsecurity running, please check that I haven't overlooked something (or misunderstood chowcheck_distro
works). The intent is that the fix would only apply to people who are in buster and have enabled, at some point, modsecurity.People who enable modsecurity for the first time get the updated config file.