ConfigServer Services Blog

New csf v2.62

Changes:

  • Fixed CIDR support issue with csf.ignore only recognising the first listed entry

New csf v2.61

Changes:

  • Fixed problem (that happened on some OS’s) with lfd not being killed by /etc/init.d/lfd

New csf v2.60

Changes and additional OS support:

  • Added log file locations to csf.conf
  • openSUSE v10 compatible (generic)
  • Debian v3.1 (sarge) compatible (generic)
  • Unbuntu v6.06 LTS compatible (generic)
  • Added installation check for the LWP (libwww-perl) perl module
  • Ran spell checker against the readme.txt file

New MSFE v3.9

Changes:

  • Fixed problem with installer where Msfe.pm wasn’t being copied on installation
  • Added new IP licensing scheme. You will need to email your order details and servers main IP address to sales@waytotheweb.com to be able to upgrade MSFE in future releases
  • Updated post-upgrade message to reflect the new route to the MSFE WHM UI
  • Added link to MSFE changelog if an upgrade is available

For this version, you can download the update from http://download.webumake.com – if you don’t have a download account, please email sales@waytotheweb.com and request one, and be sure to include the name under which you originally ordered and your servers IP address for future updates. Future versions will then be available for upgrade from within WHM.

MailScanner: Problems for Liquidweb clients

We have found that some clients hosted by Liquidweb are seeing the message “MailScanner Status: Disabled” at the top of their MailScanner front-end after a cPanel upgrade.The problem has been caused by Liquidweb’s installation of clamav rpms that modify the exim configuration each time cPanel is upgraded, thus breaking MailScanner. We have been uninstalling these rpms as part of our mailscanner install for several months now but it appears that Liquidweb has re-installed those rpms and the problem has arisen again since a recent cPanel upgrade.Fix instructions follow.If you would like us to perform the fix for you, then please log a ticket on our helpdesk with access details. There will be a $30 (half hour) charge for performing this service.Here is how to fix it:1. Remove /etc/exim.conf.local to start with a clean copy.

/bin/mv -fv /etc/exim.conf.local /etc/exim.conf.local.old/scripts/buildeximconf

2. Remove all installs and rpms of clamav and reinstall clamav.

killall clamdrpm -e clamav-db clamd clamav clamav-devel/bin/rm -Rfv /usr/bin/clam*/bin/rm -Rfv /usr/sbin/clam*/bin/rm -Rfv /usr/lib/libclam*/bin/rm -Rfv /usr/share/clam*/bin/rm -Rfv /usr/include/clam*/bin/rm -Rfv /usr/bin/freshclam*/bin/rm -Rfv /usr/etc/clamav*/bin/rm -Rfv /usr/local/bin/clam*/bin/rm -Rfv /usr/local/sbin/clam*/bin/rm -Rfv /usr/local/lib/libclam*/bin/rm -Rfv /usr/local/share/clam*/bin/rm -Rfv /usr/local/include/clam*/bin/rm -Rfv /usr/local/bin/freshclam*/bin/rm -Rfv /usr/local/etc/clamav*useradd clamavgroupadd clamavcd /root/rpmswget http://prdownloads.sourceforge.net/clamav/clamav-0.88.7.tar.gztar -xzf clamav-*cd clamav-*./configure –disable-zlib-vcheckmakemake installreplace “Example” “#Example” — /usr/local/etc/freshclam.confreplace “Example” “#Example” — /usr/local/etc/clamd.conffreshclamcd ../bin/rm -Rf clamav-*cd /root/rpms/touch /var/log/clam-update.logchown clamav:clamav /var/log/clam-update.log/scripts/perlinstaller –force Mail::ClamAV

3. Upgrade MailScanner (per instructions on website – http://www.configserver.com/cp/upgrade.html) to add correct configuration to exim.conf.local. Should be able to select option 2 (quick perl module check). You will need to do ths at the command line since you are probably already running the latest version of MailScanner.4. Re-add the dictionary attack ACL, log_selector, etc. to exim.conf.local via WHM exim configuration editor, if desired.

New csf v2.57

Changes:

  • New feature: WHM UI mod_security v1 display last X entries in the audit_log
  • New feature: WHM UI mod_security v1 edit files or directories in /usr/local/apache/conf/ that are prefixed with modsec or mod_sec
  • Tweaked the pre-configured Firewall Security Level settings

New cse v1.4

Changes:

  • Modification to work correctly current EDGE

To upgrade:

cd /usr/srcrm -fv cse.tgzwget http://www.configserver.com/free/cse.tgztar -xzf cse.tgzcd csesh install.shcd /usr/src/rm -Rfv cse*

New csf v2.54

Changes:

  • Tightened the mod_security v1 regex after the changes in v2.52

Fedora Legacy closing – FC4 no longer supported

A kindly reminder that anyone running FC4, FC3, FC2 or FC1 needs to migrate their servers as soon as possible. As this notice on the FedoraLegacy states:

In case any of you are not aware, the Fedora Legacy project is in the process of shutting down. The current model for supporting maintenance distributions is being re-examined. In the meantime, we are unable to extend support to older Fedora Core releases as we had planned. As of now, Fedora Core 4 and earlier distributions are no longer being maintained.

This means that if you’re running FC4 or lower you will no longer receive any OS updates including vital security fixes. You therefore need to migrate to a supported OS as soon as possible.We’d strongly recommend moving over to CentOSv4. If you have to use Fedora Core (and you should not use it on any production servers as it’s a development OS) then you should only currently use FC5 since cPanel don’t yet support FC6.