We're on target to discontinue support for TLS 1.0 and TLS 1.1 by end of 2018
Blog post from GitLab
GitLab announced plans to discontinue support for TLS 1.0 and 1.1 on GitLab.com and its API by December 15, 2018, in a move to enhance security, and has provided a canary production environment to test TLS 1.2 compatibility. Users can test their integrations, API tokens, and browsers using the canary environment at canary.gitlab.com to prevent disruptions, and are encouraged to complete testing before the deadline. The majority of GitLab traffic should remain unaffected as most clients already support TLS 1.2, but specific older software versions, such as Git-Credential-Manager-for-Windows before 1.14.0 and certain Red Hat and Java versions, will require updates to maintain compatibility. GitLab is committed to monitoring TLS vulnerabilities, providing updates via Twitter and security alert emails, and offering support through its security team.
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.