Server Software and Configuration Services
Changes:
For those that still insist on using Fedora Core in a production environment (which Fedora themselves do not recommend) be aware that Fedora Core 7 is due to be released in May. This means that support for Fedora Core 5 will be dropped a month later, meaning that you’ll have to upgrade your OS again unless you maintain all the installed applications yourself (a daunting task):http://fedoraproject.org/wiki/LifeCycleIf you want a more reliable (i.e. supported) OS then I would strongly recommend you choose RedHat Enterprise (3, 4 or 5) or the equivalent CentOS release, instead. These are enterprise level production OS’s which are supported for years, not months, as is the case for Fedora.
Changes:
Changes:
*ALL INSTALLATIONS SHOULD BE UPGRADED ASAP TO AVOID POTENTIAL EXPLOITATION*You can upgrade csf either through WHM or from the root shell using:
Changes:Security fix – A major security issue has been found (thanks to Jeff for informing us) in the LF_DIRWATCH code that can lead to arbitrary code being executed in the context of the user running lfd, i.e. root, if that option is enabled and a hacker has access to create a crafted filename in one of the watched directories. This update closes this hole.*ALL INSTALLATIONS SHOULD BE UPGRADED ASAP TO AVOID POTENTIAL EXPLOITATION*You can upgrade csf either through WHM or from the root shell using:
ClamAV have released a new version with security fixes. It is advised that everyone upgrade to this new version, which you can now do through the MailScanner WHM UI.
Changes in this release include some security fixes in CHM, CAB and PDF code and better handling of network problems in freshclam.Please see ChangeLog for complete list of changes. **Important note**: on April 16th CHM, CAB and PDF handlers will be disabled for 0.90 and 0.90.1 users through the dynamic engine configuration module (DCONF). Please upgrade to 0.90.2 immediately.
Changes:
Changes:
ClamAV have released a new version that fixes a raft of things that they broke with the v0.90 release a few days ago. We will be releasing a new version of the MailScanner installer script shortly that fixes an incompatibility in MailScanner with the new v0.9* version of ClamAV.
The day we release a patch workaround the Mail::ClamAV developer has finally released fixed code for ClamAV v0.90. It will take some time to get around all the cpan.org mirrors, but you can install it from source easily enough and then revert to virus scanners = clamavmodule in MailScanner.conf
Virus Scanners = clamavmodule