News

Home/News

eFa 3.0.2.3 Update Released

The 3.0.2.3 update is now available.

We would also like to thank everyone for their support and contributions to this project. :clap:

The following issues have been fixed (hopefully) in 3.0.2.3:

Issue #367 Bug – mod_security disable id 981320 (and 981317)
Issue #369 Bug – Variable type mismatch in viewmail.php

Configurable mod_security option added to EFA-Configure
Update MailWatch to resolve various issues found after 3.0.2.2
Includes session enhancements and configurable session timeouts

 

#################### Important Security Notice ########################

/// Everyone is STRONGLY encouraged to update from 3.0.1.8 and below NOW \ \ \

A recent set of vulnerabilities have been discovered in the MailWatch and
SGWI interfaces that can allow an attacker to escalate privileges in eFa.

Because of these vulnerabilities, if you are using the same password for
the console as you are for MailWatch (many folks are), please take a moment
to make your MailWatch admin password different from the console.
Doing so will limit the success of a shared credential attack via MailWatch
on eFa to gain root access.

If you cannnot update or have problems, the following steps are
strongly recommended to keep your appliance safe until you can update
successfully:

1) Rotate your admin passwords in the console and MailWatch UI and make
each one different than the other to prevent a shared credential
attack.

2) Install mod_security and mod_evasive to provide some security in front
of the vulnerable code.

3) Inform your MailWatch users (especially admins) to avoid opening multiple
tabs and performing general web browsing while working in MailWatch

###################### How To Update ##################################

It is recommended that you suspend your mail flow and snapshot prior
to updating or to back up the entire appliance.

1) Stop mail flow temporarily (at firewalls/mailservers)
2) Snapshot your VM and its memory using your hypervisor tools
3) If the update fails for any reason, collect relevant logs or screen
outputs/screenshots and revert to your snapshot
4) Report failure at https://forum.efa-project.org

Launch EFA-Configure from console or secure shell

(sudo /usr/local/sbin/EFA-Configure)

Choose option 14) Update Now

The first time you run this update, the kernel may update. If this
happens, the script will halt to give you an opportunity to restart.
After restarting and booting to the new kernel, rerun EFA-Update to
continue the update process to 3.0.2.3.

EFA-Update will not proceed until you are running on the latest
kernel. This is to ensure that open-vm-tools updates appropriately
if present.

eFa 3.0.2.2 Update Released

The 3.0.2.2 update is now available.

We would also like to thank everyone for their support and contributions to this project. :clap:

The following issues have been fixed (hopefully) in 3.0.2.2:

Issue #357 Bug – Fonts Not Rendering in MailWatch
Issue #358 Bug – Certain emails from detail.php do not populate B/W Lists
Issue #362 Bug – mod_security disable id 981247
Issue #363 Bug – Check for failed yum kernel update
Issue #366 Bug – Clear SpamAssassin-Temp

MailWatch update to resolve timeout issues and directory traversal
#################### Important Security Notice ########################

/// Everyone is STRONGLY encouraged to update from 3.0.1.8 and below NOW \ \ \

A recent set of vulnerabilities have been discovered in the MailWatch and
SGWI interfaces that can allow an attacker to escalate privileges in eFa.

Because of these vulnerabilities, if you are using the same password for
the console as you are for MailWatch (many folks are), please take a moment
to make your MailWatch admin password different from the console.
Doing so will limit the success of a shared credential attack via MailWatch
on eFa to gain root access.

If you cannnot update or have problems, the following steps are
strongly recommended to keep your appliance safe until you can update
successfully:

1) Rotate your admin passwords in the console and MailWatch UI and make
each one different than the other to prevent a shared credential
attack.

2) Install mod_security and mod_evasive to provide some security in front
of the vulnerable code.

3) Inform your MailWatch users (especially admins) to avoid opening multiple
tabs and performing general web browsing while working in MailWatch

###################### How To Update ##################################

It is recommended that you suspend your mail flow and snapshot prior
to updating or to back up the entire appliance.

1) Stop mail flow temporarily (at firewalls/mailservers)
2) Snapshot your VM and its memory using your hypervisor tools
3) If the update fails for any reason, collect relevant logs or screen
outputs/screenshots and revert to your snapshot
4) Report failure at https://forum.efa-project.org

Launch EFA-Configure from console or secure shell

(sudo /usr/local/sbin/EFA-Configure)

Choose option 14) Update Now

The first time you run this update, the kernel may update. If this
happens, the script will halt to give you an opportunity to restart.
After restarting and booting to the new kernel, rerun EFA-Update to
continue the update process to 3.0.2.2.

EFA-Update will not proceed until you are running on the latest
kernel. This is to ensure that open-vm-tools updates appropriately
if present.

eFa 3.0.1.9 Security Update Released

The 3.0.1.9 security update is now available.

We would also like to thank everyone for their support and contributions to this project.

A big thanks to the MailWatch team for making security fixes possible!

The following issues have been fixed (hopefully) in 3.0.1.9:

– Added Apache mod_security by default
– Added Apache X-XSS-Protection header
– Updated MailWatch and Sqlgrey Web Interface (Security Fixes)
– Changed and updated database engine to MariaDB (10.1)

#################### Important Security Notice ########################

/////// Everyone is STRONGLY encouraged to update to 3.0.1.9 NOW \\\\\\\\\

A recent set of vulnerabilities have been discovered in the MailWatch and
SGWI interfaces that can allow an attacker to escalate privileges in eFa.

Because of these vulnerabilities, if you are using the same password for
the console as you are for MailWatch (many folks are), please take a moment
to make your MailWatch admin password different from the console.
Doing so will limit the success of a shared credential attack via MailWatch
on eFa to gain root access.

If you cannnot update to 3.0.1.9 or have problems, the following steps are
strongly recommended to keep your appliance safe until you can update
successfully:

1) Rotate your admin passwords in the console and MailWatch UI and make
each one different than the other to prevent a shared credential
attack.

2) Install mod_security and mod_evasive to provide some security in front
of the vulnerable code.

3) Inform your MailWatch users (especially admins) to avoid opening multiple
tabs and performing general web browsing while working in MailWatch

##################### Important database changes ######################

MailWatch 1.2.1-dev has utf8mb4 character set support.
CentOS 6.8 lacks this support in the stock mysql rpms.
Therefore, upgrades to 3.0.1.9 will migrate the database from mysql
to MariaDB 10.1. This may be a big jump for some users and may want
to perform additional testing prior to upgrading.

###################### How To Update ##################################

It is recommended that you suspend your mail flow and snapshot prior
to updating or to back up the entire appliance.

1) Stop mail flow temporarily (at firewalls/mailservers)
2) Snapshot your VM and its memory using your hypervisor tools
3) If the update fails for any reason, collect relevant logs or screen
outputs/screenshots and revert to your snapshot
4) Report failure at https://forum.efa-project.org

Launch EFA-Configure from console or secure shell

(sudo /usr/local/sbin/EFA-Configure)

Choose option 14) Update Now

The first time you run this update, the kernel may update. If this
happens, the script will halt to give you an opportunity to restart.
After restarting and booting to the new kernel, rerun EFA-Update to
continue the update process to 3.0.1.9.

EFA-Update will not proceed until you are running on the latest
kernel. This is to ensure that open-vm-tools updates appropriately
if present.

eFa3 Code Freeze

Greetings eFa Users!

eFa started as a replacement for ESVA when that project died.

As some of you may know, that was a long time ago. In fact, eFa3 is now really starting to show its age. Despite it being updated, we are still on CentOS 6.
It is time to move forward with new development. :dance:

Therefore, we are announcing a pending code freeze for eFa3 so that we can begin work on eFa4.

No new features or enhancements will be added to eFa. However, bug fixes may be released as needed depending on the severity of the issue.
We look forward to many new developments and will keep you posted!

eFa 3.0.1.8 Released

The 3.0.1.8 update is now available.

We would also like to thank everyone for their support and contributions to this project. :clap:

The following issues have been fixed (hopefully) in 3.0.1.8:

Issue #347 Bug – Missing defines in latest MailWatch

It is recommended that you suspend your mail flow and snapshot prior
to updating or to back up the entire appliance.

1) Stop mail flow temporarily (at firewalls/mailservers)
2) Snapshot your VM and its memory using your hypervisor tools
3) If the update fails for any reason, collect relevant logs or screen
outputs/screenshots and revert to your snapshot
4) Report failure at https://forum.efa-project.org

Launch EFA-Configure from console or secure shell

(sudo /usr/local/sbin/EFA-Configure)

Choose option 14) Update Now

The first time you run this update, the kernel may update. If this
happens, the script will halt to give you an opportunity to restart.
After restarting and booting to the new kernel, rerun EFA-Update to
continue the update process to 3.0.1.8.

EFA-Update will not proceed until you are running on the latest kernel. This is to ensure that open-vm-tools updates appropriately if present.

After updating, please run “Update GeoIP Database” update as soon as possible from MailWatch under Tools/Links.