Όλες οι εκδόσεις
0.1.0-beta.27
This release brings 5 fixes.
Διορθώσεις σφαλμάτων
- The update history marks an update the scheduler installed as automatic. With automatic updates on, a release the daily scheduler installed was listed on the Updates page's History tab as a manual update, so an operator could not tell which updates they had started. The scheduler's installs, completed or failed, are now recorded as automatic; updates started from the panel stay manual.
- A successful installation no longer ends with false port and PHP-FPM warnings. The installer's final check could report running services as "not detected on port ..." and an installed PHP-FPM version as "not installed on this OS", then close a successful installation with "Some warnings detected. Installation may need manual adjustments." The check now reads the lists of listening ports and installed services in full before searching them, so these lines appear only when a service is really missing.
- The WAF engine version is recognised on Ubuntu 24.04. On Ubuntu 24.04 the installer reported "libmodsecurity version unknown" and the agent could not read the WAF engine's version, because the package is named libmodsecurity3t64 there. The rule set was still complete on new 24.04 servers. The installer and the agent now read the version under either package name, so a server upgraded from Ubuntu 22.04 to 24.04 also gets back the rule file that was set aside for the older engine.
- The WAF custom rules placeholder describes where hand-written rules go. The file the installer writes into /etc/modsecurity/custom/ said custom rules could be added from the admin panel, which has no such page. It now says that rules written by hand go into additional .conf files in that folder and that WHost never rewrites them.
- Rate-limit bans of a new rule appear in the security log. When a rate-limit rule was created and an address went over it within its first half minute, the ban worked but never appeared under Firewall, Security Logs, so the administrator could not see it. Every ban of a rule created while the agent runs is now recorded; bans that existed before the agent started are still not counted twice.