Last Modified: Sep 13, 2023
Known Affected Versions:
13.1.0, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 13.1.1, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 14.1.2, 18.104.22.168, 22.214.171.124
15.0.0, 126.96.36.199, 188.8.131.52
Opened: Nov 16, 2018 Severity: 3-Major
An HTTPS monitor using a client certificate configured in the server-ssl profile fails to send the certificate during the SSL handshake. A tcpdump shows a 0-byte certificate being sent.
SSL handshake might fail to complete and the HTTPS monitor fails.
-- In-tmm monitoring is disabled (default). -- The server-ssl profile has been modified but without changing the configured certificate or key. The resulting message passed from mcpd to bigd will contain only the incremental modification to the profile, which bigd treats as a complete profile, meaning that it is possible for the certificate and key parameters to be lost.
Restart bigd process by running the following command: bigstart restart bigd
mcpd now sends the full profile configuration to bigd upon modification.