Zimbra Collaboration 7 or previous, zmlicense error handshake failure: Difference between revisions
(Created page with "{{BC|Certified}} __FORCETOC__ <div class="col-md-12 ibox-content"> =Zimbra Collaboration 7 or previous, zmlicense error handshake failure= {{KB|{{ZC}}|{{ZCS 8.0}}|{{ZCS 7.0}}|...") |
|||
Line 7: | Line 7: | ||
== Purpose == | == Purpose == | ||
Zimbra is aware of all the SSLv3 vulnerabilities. In our internal work for our Licensing Portal, Zimbra has | Zimbra is aware of all the SSLv3 vulnerabilities. In our internal work for our Licensing Portal, Zimbra has disabled SSLv3 due to the various security vulnerabilities that exist in the protocol. | ||
Customers that are running Zimbra Collaboration 7 or previous versions, are going to be affected when they try to activate their licenses, even if the license is properly issued and still valid. | Customers that are running Zimbra Collaboration 7 or previous versions, are going to be affected when they try to activate their licenses, even if the license is properly issued and still valid. | ||
Line 16: | Line 16: | ||
Release 7.2.7_GA_2942.RHEL6_64_20140314190059 CentOS6_64 NETWORK edition. | Release 7.2.7_GA_2942.RHEL6_64_20140314190059 CentOS6_64 NETWORK edition. | ||
Let's try now to see if the | Let's try now to see if the license is activated or not in a fresh install: | ||
$ zmlicense -c | $ zmlicense -c | ||
license not activated for 7.2.7_GA_2942 | license not activated for 7.2.7_GA_2942 | ||
If you try to activate it, you will see the next error, due the | If you try to activate it, you will see the next error, due the security reasons we've explained before: | ||
$ zmlicense -a | $ zmlicense -a | ||
system failure: javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure | system failure: javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure |
Revision as of 15:52, 16 October 2015
Zimbra Collaboration 7 or previous, zmlicense error handshake failure
Purpose
Zimbra is aware of all the SSLv3 vulnerabilities. In our internal work for our Licensing Portal, Zimbra has disabled SSLv3 due to the various security vulnerabilities that exist in the protocol. Customers that are running Zimbra Collaboration 7 or previous versions, are going to be affected when they try to activate their licenses, even if the license is properly issued and still valid.
Error when try to active the license in ZCS 7 or previous
In this example, you can see ZCS 7.2.7 running over a CentOS 6:
# su - zimbra $ zmcontrol -v Release 7.2.7_GA_2942.RHEL6_64_20140314190059 CentOS6_64 NETWORK edition.
Let's try now to see if the license is activated or not in a fresh install:
$ zmlicense -c license not activated for 7.2.7_GA_2942
If you try to activate it, you will see the next error, due the security reasons we've explained before:
$ zmlicense -a system failure: javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure
Resolution
1.- Get the information required (fingerprint, activation ID, license ID and version) for the manual activation from the Admin Console at:
Global Settings ⇒ License ⇒ Manually Activate License
2.- Go to https://support.zimbra.com and log in, go to the license page.
3.- Enter the required information and download the .xml file.
4.- Upload the .xml file to the Zimbra server and enter:
zmlicense -A /path/to/activation/file
4.1.- You can do it as well using the Admin Console in Global Settings ⇒ License ⇒ Manually Activate License
5.- Check for successful activation with:
zmlicense -t
If you have any problem, please don't hesitate contact the Zimbra Support Team.
Additional Content
You can read the Manual Activation Wiki: