SHA-1 in HTTPS on GitHub sunset
By Steven Van ·
GitHub has completed its planned removal of SHA-1 from HTTPS on github.com and partner CDNs; GitHub Enterprise Server is unaffected.
GitHub has disabled SHA-1 in HTTPS for GitHub on schedule, following the sunset it announced in April. The change applies to github.com and partner CDNs, including GitHub Enterprise Cloud and GitHub Enterprise Cloud with Data Residency; GitHub Enterprise Server is unaffected.
Anything connecting over HTTPS with SHA-1, whether a browser, an API client, or a Git client, will now fail to connect unless it supports newer TLS algorithms. GitHub's original announcement recommended using an up-to-date browser, a modern API client library, and a recent version of Git with an up-to-date TLS backend such as OpenSSL.
