Applies to: WAVE
Summary
Questions sometimes arise about the TLS versions used in WAVE, especially after penetration tests reveal multiple versions. These versions are not actively in use, and are maintained solely for backward compatibility with upcoming updates for third-party integrations. This strategy allows us to enhance our security measures while ensuring smooth compatibility with essential external systems. This article shows how to check and/or change the TLS version in WAVE.
Checking the Specific TLS Version
Server - Client Communication
With Wireshark, you can capture packets from one application to another application, which enables you to check the traffic between our Server application and Desktop Client applications.
To determine the version:
- Start Wireshark on Desktop Client.
- Set the Server IP address as the Host filter.
-
Apply a display filter with the following parameters:
tcp.port == 7001 && tlsThis display filter displays the TCP communication over port 7001 (the default port of the VMS) and in particular the TLS protocol.
- Check the column Protocol; TLS is used.
- To determine which TLS version can be used, and which one is used, you can check the Packet Details panel.
To find the applicable information:
- Select a Client Hello packet.
- Locate Transport Layer Security in the Packet Details panel.
- Expand the options:
- TLSv1.3 Record Later: Handshake Protocol: Client Hello
- Handshake Protocol
- Extension: supported_versions
All possible versions of the TLS protocol from the Client side are located here, which enables connection to older versions of the VMS as well.
To verify which TLS version actually is used by the system, and what version is used for the connection between the Desktop Client and Server:
- Select a Server Hello packet.
- Locate Transport Layer Security in the Packet Details panel.
- If you expand the content, check for Supported Version and you will see the TLS version that is used in this case, which is Supported Version: TLS 1.3 (0x0304). In TLS 1.3, the record layer still shows Version: TLS 1.2 (0x0303) for compatibility with older systems.
This value does not indicate the actual protocol version that is used, but is kept for legacy reasons. The real TLS version is negotiated in the handshake’s supported_versions extension.
Browser - Server Communication
With the browser, you can check the TLS version that is used when you navigate to the WebAdmin or the Cloud Client portal.
For Firefox
To check the version:
- Open the Developer Tools (Ctrl+Shift+I).
- Select the Network tab.
-
Select an item in the results and select the Security tab in the pane on the right.
NOTE: If the Security tab is not available, select another item. - Under Security, check the Connection and Protocol version to determine which TLS protocol is used.
For Chrome
To check the version:
- Open the Developer Tools (Ctrl+Shift+I).
- Select the Security tab.
- Navigate to the WebAdmin or Cloud Client portal.
- Under Security, check the results for the section Connection to check which TLS protocol is used.
Changing the Default TLS Version
Used by the Application
By default, TLS 1.3 is used. However, it is possible to change the TLS versions by changing the value in the server configuration files.
NOTE: Lowering these values has an impact on the overall security of the system and
is never recommended.
For Windows
- Open the registry editor and navigate to:
HKEY_LOCAL_MACHINE\SOFTWARE\Hanwha\ Hanwha Media Server
- Add a string value allowedSslVersions and put the value TLSv1.2.
- Restart the WAVE mediaserver defaultMediaServer service.
For Linux
- Navigate to:
/opt/ Hanwha /mediaserver/etc/
- Open the mediaserver.conf and add the following entry: allowedSslVersions=tls1_2
- Restart the Hanwha-mediaserver service.
Used by the Browser
Most browsers use TLS 1.2 or newer as their default value to prohibit you from using previous versions of TLS. Although we do not recommend changing these values, with, for example Firefox, you can change these values for the sake of backward compatibility.
For Firefox
When you navigate to about:config and search for security.tls.version.m, notice that the default values are 3 for the minimum version and 4 for the maximum version. This means that TLS 1.2 is used as a minimum and TLS 1.3 as the maximum. To change these values, you can use the following parameters to change minimum and maximum values.
1 = TLS 1.0 (insecure)
2 = TLS 1.1 (insecure)
3 = TLS 1.2
4 = TLS 1.3
For Chrome
Chrome does not have this option, but it is possible to force a certain TLS version by starting Chrome through the terminal.
For Windows
- Open the Command Prompt window.
- Enter the following command:
"C:\Program Files\Google\Chrome\Application\chrome.exe" --ssl-version-min=tls1.3
For macOS
- Open the terminal window.
- Enter the following command:
/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --ssl-version-min=tls1.3
For Linux
- Open the terminal window.
- Enter the following command:
google-chrome --ssl-version-min=tls1.3
NOTE: If the values of your browser do not match with values in the mediaserver
configuration file, you cannot connect to the system. Confirming the Changes
To confirm these changes, you can use the following commands:
For Windows
Open the command prompt and enter the following command:
reg query "HKEY_LOCAL_MACHINE\SOFTWARE\ Hanwha \ Hanwha Media Server" /v "allowedSslVersions"
For Linux
Open the Terminal and enter the following command:
grep "allowedSslVersions" /opt/ Hanwha /mediaserver/etc/mediaserver.conf