Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

TLS protocol configuration options for vSphere Replication 8.x (70883)

Last Updated: 11/2/2020Categories: InformationalTotal Views: 6607Language:
Chinese (Simplified)JapaneseEnglish

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Details

In vSphere Replication 8.1, 8.2, and 8.3, the TLS protocol versions, 1.1, and 1.2 are enabled by default. The purpose of this article is to guide a customer through modifying the TLS protocols on the individual services of vSphere Replication.

Solution

To disable TLSv1.1 use the following steps.

Service

Port

Configuration steps

Configuration steps for vSphere Replication Management Service (hms)

8043

Configuration steps for hms service.

Configuration steps for vSphere Replication service (hbrsrv)

8123

Configuration steps for hbrsrv service.

Configuration steps for VMware Virtual Appliance Management Interface (VAMI)

5480

Configuration steps for vami service.

Configuration steps for Site Recovery UI

443

Configuration steps for Site Recovery UI

NOTE: Always make a backup copy of the configuration file before you start editing.

Configuration steps for vSphere Replication Management Service - port 8043

Log in to the vSphere Replication appliance using PuTTY.

Open the file /opt/vmware/hms/conf/hms-configuration.xml in an editor and change the value of hms-ssl-enabled-protocols to TLSv1.2.

Save the file.

Restart hms service.

service hms restart

Configuration steps for vSphere Replication service - port 8123

Log in to vSphere Relication Appliance and vSphere Replication Server using PuTTY.

Open the file /etc/vmware/hbrsrv.xml in an editor, locate the tag <vmacore><ssl> and add <sslOptions>386023424</sslOptions> in to disable TLSv1.1

<vmacore> <ssl> <sslOptions>117587968</sslOptions> </ssl> </vmacore>

Save the file.

Restart the service.

service hbrsrv restart

SSL/TLS Protocols

Value

Disable SSLv3 + Disable TLSv1.0

117587968

Disable SSLv3 + Disable TLSv1.0 + Disable TLSv1.1

386023424

Re-Enable all versions of TLS (1.0,1.1 and 1.2)

50479104

Configuration steps for VMware Virtual Appliance Management Interface (VAMI) - port 5480

Go to /opt/vmware/etc/lighttpd/lighttpd.conf.

Create a backup copy of the file.

Open the file in an editor and search for the ssl.use-tlsv11.

To disable TLS 1.1 make sure that: ssl.use-sslv2, ssl.use-tlsv10, ssl.use-tlsv11 properties are all having a value of "disable" and ssl.use-tlsv12 have a value of "enable".

Configuration steps for Site Recovery UI - Port 443

Site Recovery UI runs in an Apache Tomcat server and to change the supported TLS version perform the following steps on an HMS appliance:

Open Apache Tomcat configuration file with a text editor.

vi /var/opt/apache-tomcat/conf/server.xml

Look for a 'Connector' tag that defines a tomcat connector responding on address="::" and port="8443". It should also have a 'SSLHostConfig' tag as a child. For example it should look like:

<Connector SSLEnabled="true" Secure="true" address="::" maxThreads="150" port="8443" protocol="org.apache.coyote.http11.Http11NioProtocol">
<SSLHostConfig ciphers="!aNULL:kECDH+AESGCM:ECDH+AESGCM:RSA+AESGCM:kECDH+AES:ECDH+AES:RSA+AES" protocols="TLSv1.2">
<Certificate certificateKeystoreFile="lib/hms-keystore.jks" certificateKeystorePassword="H55MSDVcNUdsAwlP" type="RSA" />
</SSLHostConfig>
</Connector>

In the SSLHostConfig xml tag look for an argument named 'protocols' this is what defines the supported TLS versions. For example 'TLSv1.1+TLSv1.2' means that TLS 1.1 and TLS 1.2 are both supported and can be used
for connection. To only allow TLS 1.2 set the value to 'TLSv1.2'.

After modifying server.xml file you need to restart tomcat service.

service tomcat restart

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
VMware Cloud on AWS の Cohesity データ保護ソリューション (70921)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere Replication

VMware vSphere

Related Versions:

VMware vSphere Replication 8.x

Take Our Survey

Support Assistant