tls.VersionSSL30 is deprecated.

[xiekeyi98]

Bug Report

In

tidb/sessionctx/variable/statusvar.go

Lines 100 to 105 in b743208

	var tlsVersionString = map[uint16]string{
	tls.VersionSSL30: "SSLv3",
	tls.VersionTLS10: "TLSv1",
	tls.VersionTLS11: "TLSv1.1",
	tls.VersionTLS12: "TLSv1.2",
	}

we used tls.VersionSSL30 ,but sslv3 is cryptographically broken and will remove in Go1.14 .

See golang/go#32716 for detail.

[ghost]

Confirming this is still an issue in master:

tidb/sessionctx/variable/statusvar.go

Lines 104 to 111 in ace80c7

	// Taken from https://github.com/openssl/openssl/blob/c784a838e0947fcca761ee62def7d077dc06d37f/include/openssl/ssl.h#L141 .
	var tlsVersionString = map[uint16]string{
	tls.VersionSSL30: "SSLv3",
	tls.VersionTLS10: "TLSv1",
	tls.VersionTLS11: "TLSv1.1",
	tls.VersionTLS12: "TLSv1.2",
	tls.VersionTLS13: "TLSv1.3",
	}

[dveeden]

From https://docs.pingcap.com/tidb/stable/enable-tls-between-clients-and-servers:
"Because the SSL protocol has known security vulnerabilities, TiDB does not support it."

So I wonder why it's there in the first place. Removing it here should be fine.

[ti-srebot]

Please edit this comment or add a new comment to complete the following information

Not a bug

1. Remove the 'type/bug' label
2. Add notes to indicate why it is not a bug

Duplicate bug

1. Add the 'type/duplicate' label
2. Add the link to the original bug

Bug

Note: Make Sure that 'component', and 'severity' labels are added
Example for how to fill out the template: #20100

1. Root Cause Analysis (RCA) (optional)

2. Symptom (optional)

3. All Trigger Conditions (optional)

4. Workaround (optional)

5. Affected versions

6. Fixed versions