[{"data":1,"prerenderedAt":86},["ShallowReactive",2],{"blog-github-disables-sha-1-in-https-to-strengthen-security":3},{"_path":4,"_dir":5,"_draft":6,"_partial":6,"_locale":7,"title":8,"description":9,"date":10,"tags":11,"cover":16,"body":17,"_type":80,"_id":81,"_source":82,"_file":83,"_stem":84,"_extension":85},"/blog/github-disables-sha-1-in-https-to-strengthen-security","blog",false,"","GitHub Disables SHA-1 in HTTPS to Strengthen Security","GitHub phases out SHA-1 in HTTPS connections as part of planned security improvements.","2026-09-16",[12,13,14,15],"security","github","HTTPS","cryptography",true,{"type":18,"children":19,"toc":73},"root",[20,29,35,41,46,52,57,63,68],{"type":21,"tag":22,"props":23,"children":25},"element","h2",{"id":24},"phasing-out-sha-1-a-necessary-security-upgrade",[26],{"type":27,"value":28},"text","Phasing Out SHA-1: A Necessary Security Upgrade",{"type":21,"tag":30,"props":31,"children":32},"p",{},[33],{"type":27,"value":34},"On September 15, 2026, GitHub disabled SHA-1 hashing algorithm in HTTPS connections for github.com and its partners. This decision aligns with the broader industry move to retire SHA-1 due to its vulnerabilities.",{"type":21,"tag":22,"props":36,"children":38},{"id":37},"why-disable-sha-1",[39],{"type":27,"value":40},"Why Disable SHA-1?",{"type":21,"tag":30,"props":42,"children":43},{},[44],{"type":27,"value":45},"SHA-1 has been considered weak and susceptible to collision attacks for years. Continuing to support it can expose users to risks such as man-in-the-middle attacks, compromising privacy and data integrity.",{"type":21,"tag":22,"props":47,"children":49},{"id":48},"what-this-means-for-users-and-partners",[50],{"type":27,"value":51},"What This Means for Users and Partners",{"type":21,"tag":30,"props":53,"children":54},{},[55],{"type":27,"value":56},"By disabling SHA-1, GitHub ensures that all HTTPS connections use more secure cryptographic algorithms like SHA-256. Partners and users are encouraged to verify their systems support modern protocols to maintain seamless connectivity.",{"type":21,"tag":22,"props":58,"children":60},{"id":59},"looking-ahead",[61],{"type":27,"value":62},"Looking Ahead",{"type":21,"tag":30,"props":64,"children":65},{},[66],{"type":27,"value":67},"This change is part of an ongoing effort to maintain the highest standards of security, fostering trust and reliability for the GitHub platform and its ecosystem.",{"type":21,"tag":30,"props":69,"children":70},{},[71],{"type":27,"value":72},"Staying informed about cryptographic best practices remains essential for developers and organizations working in today's security landscape.",{"title":7,"searchDepth":74,"depth":74,"links":75},2,[76,77,78,79],{"id":24,"depth":74,"text":28},{"id":37,"depth":74,"text":40},{"id":48,"depth":74,"text":51},{"id":59,"depth":74,"text":62},"markdown","content:blog:github-disables-sha-1-in-https-to-strengthen-security.md","content","blog/github-disables-sha-1-in-https-to-strengthen-security.md","blog/github-disables-sha-1-in-https-to-strengthen-security","md",1789543116373]