Using a deprecated function, variable, constant or field GO-W1009
Anti-pattern
Major
5 months ago
—
2 years old
tls.VersionSSL30 has been deprecated since Go 1.13 because it shouldn't be used: SSLv3 is cryptographically broken, and is no longer supported by this package. See golang.org/issue/32716.
299 tls.TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,
300 }
301 versions = map[string]uint16{
302 "SSL3.0": tls.VersionSSL30,303 "TLS10": tls.VersionTLS10,
304 "TLS11": tls.VersionTLS11,
305 "TLS12": tls.VersionTLS12,tls.VersionSSL30 has been deprecated since Go 1.13 because it shouldn't be used: SSLv3 is cryptographically broken, and is no longer supported by this package. See golang.org/issue/32716.
337 in string
338 out uint16
339 }{
340 {in: "SSL3.0", out: tls.VersionSSL30},341 {in: "TLS10", out: tls.VersionTLS10},
342 {in: "TLS11", out: tls.VersionTLS11},
343 {in: "TLS12", out: tls.VersionTLS12},
Description
Sometimes a function, variable, constant, field, or whole package becomes redundant or unnecessary but must be kept for compatibility with existing programs. These should not be used except for compatibility with legacy systems.