• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.

[PPP-15880] Issue with Atomic rules (subscription)

LinqLOL

Basic Pleskian
We running into problems with modsecurity when enabling the Atomic (subscription) rules it's seems not to work (not even logging to the modsec log). I test it with /index.php?foo=../../passwd

When I switch to Atomic Basic ModSecurity rule set I get an nice 403 and the modsec log is being filled.

When looking into the /etc/httpd/conf/modsecurity.d/rules/atomic/modsec I see all the files have an old modification time. So I wanted to find out if the rules got updated anyways. The /etc/cron.daily/asl cron is executed daily as I can see in the cron logs.

Running aum -u manually does not show errors, just:
Code:
Checking versions ...

        ASL version is current:                            [PASS]
        MODSEC rules are current: 201506041534             [PASS]
        Generating report ...

        Finished

But the rules in /etc/httpd/conf/modsecurity.d/rules/atomic/modsec are not updated! Also after the aum -u I see the the original modsecurity is replaced with the rpm from Atomicorp.

We see this behaviour on a server which has never had used modsecurity before.
Could anyone tell me whats wrong here?
 
@igor this has todo with #PPP-15880 you have any clue when this will be fixed?!?

ps. I hate these regression bugs! Do some proper QA
 
Back
Top