This repository has been archived by the owner on Jan 27, 2024. It is now read-only.
/
RELEASENOTES
114 lines (83 loc) · 4.63 KB
/
RELEASENOTES
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
######################################################################
# EFA 3.0.2.6 RELEASE NOTES
######################################################################
# Copyright (C) 2015-2018 https://efa-project.org
#
# This program is free software: you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation, either version 3 of the License, or
# (at your option) any later version.
#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with this program. If not, see <http://www.gnu.org/licenses/>.
#######################################################################
Welcome to EFA Version 3.0.2.6!
Many thanks goes to the developers of EFA and maintainers of all
3rd party packages!
These release notes will help guide you through the 3.0.2.6 update.
Many fixes and enhancements have been made to EFA. Please review the
CHANGELOG for further information.
https://raw.githubusercontent.com/E-F-A/v3/3.0.2.6/CHANGELOG
###################### 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.6.
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.
#######################################################################
############# Important Info -- Deprecation Warning ###################
Due to security issues found in the handling of domain admins, users
and domain admins are required to be full email addresses. This
requirement can be disabled in /var/www/html/mailscanner/conf.php for
backward compatibility. However, doing so reduces the security of the
system. The security problem is that domain admins have the ability to
elevate and downgrade privileges of other admins and domain admins.
################ Important Info -- Custom Tweaks ######################
Many EFA users have modified their EFA installations and made tweaks
that may "disappear" after an update to 3.0.2.6.
Updated files have been automatically backed up to the following
location:
/var/EFA/backup/
(Other versions may be present if updating from an older version)
Users who had prior 3rd party certs in-place on eFa 3.0.2.4 or lower
are overridden by the upgrade to eFa 3.0.2.6. This is due to the
regeneration of the self-signed cert. After the upgrade, and if you
were using a 3rd party cert, please make sure to update your paths
accordingly for Postfix and Apache to reflect the original paths.
Future updates beyond 3.0.2.6 will leave exisitng cert paths alone,
pending no major security tweaks required to secure systems.
########################## Known Issues ###############################
1) If you are running commercial VMware-Tools, open-vm-tools may
install itself after updating to 3.0.2.6. Reapply VMware-Tools
after updating to 3.0.2.6. Run the following command to remove
open-vm-tools:
sudo rpm -e open-vm-tools
2) If you updated from versions prior to 3.0.2.5, manual intervention
for clamav-unofficial-sigs may be necessary. Examine
/etc/clamav-unofficial-sigs and update conf files.
If rpmnew files are present, move your customizations (if any) to them.
and replace the old conf files. For example:
mv /etc/clamav-unofficial-sigs/master.conf /etc/clamav-unofficial-sigs/master.conf.old
mv /etc/clamav-unofficial-sigs/master.conf.rpmnew /etc/clamav-unofficial-sigs/master.conf
#######################################################################
########################## Reporting Issues ###########################
Please visit https://forum.efa-project.org and report bugs under the
3.x Bugs forum.
#######################################################################