Support for TLS 1.0 and 1.1 discontinued on GitLab.com and GitLab API on 2018-12-15

GitLab announced that, in line with the PCI Security Standards Council mandate, they discontinued support for TLS 1.0 and 1.1 on GitLab.com and their GitLab API as of December 15, 2018, requiring clients to use TLS 1.2 for enhanced security. This change, aimed at evolving their security posture and complying with the Payment Card Industry Data Security Standard (PCI DSS) 3.1, is part of their broader strategy to eliminate outdated protocols prone to attacks. While most traffic to GitLab.com uses up-to-date clients supporting TLS 1.2, some users with older systems, such as Git-Credential-Manager-for-Windows versions before 1.14.0, Red Hat versions before 6.8 and 7.2, JDK 6 or earlier, and older versions of Visual Studio 2017, may need updates to maintain compatibility. Self-managed installations will see these changes in the upcoming major release 12.0, scheduled for March 22, 2019, and GitLab encourages users experiencing disruptions to contact their support or security teams for assistance.

No tracked trend matches for this post yet.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.