[{"data":1,"prerenderedAt":89},["ShallowReactive",2],{"blog-sunsetting-sha-1-in-https-on-github":3},{"_path":4,"_dir":5,"_draft":6,"_partial":6,"_locale":7,"title":8,"description":9,"date":10,"tags":11,"cover":16,"body":17,"_type":83,"_id":84,"_source":85,"_file":86,"_stem":87,"_extension":88},"/blog/sunsetting-sha-1-in-https-on-github","blog",false,"","Sunsetting SHA-1 in HTTPS on GitHub","GitHub is enhancing HTTPS security by removing SHA-1 support to mitigate vulnerabilities.","2026-04-20",[12,13,14,15],"security","github","https","cryptography",true,{"type":18,"children":19,"toc":77},"root",[20,29,35,41,46,52,72],{"type":21,"tag":22,"props":23,"children":25},"element","h2",{"id":24},"why-is-github-removing-sha-1",[26],{"type":27,"value":28},"text","Why Is GitHub Removing SHA-1?",{"type":21,"tag":30,"props":31,"children":32},"p",{},[33],{"type":27,"value":34},"SHA-1, an aging cryptographic hash function, has known vulnerabilities that can compromise secure connections. GitHub's decision to sunset SHA-1 in HTTPS connections aims to protect users by enforcing stronger cryptographic standards.",{"type":21,"tag":22,"props":36,"children":38},{"id":37},"what-this-means-for-users-and-developers",[39],{"type":27,"value":40},"What This Means for Users and Developers",{"type":21,"tag":30,"props":42,"children":43},{},[44],{"type":27,"value":45},"Browsers and software interacting with GitHub’s website and content delivery networks (CDNs) must support newer hash algorithms. Users relying on outdated clients that still use SHA-1 may experience access issues.",{"type":21,"tag":22,"props":47,"children":49},{"id":48},"preparing-for-the-change",[50],{"type":27,"value":51},"Preparing for the Change",{"type":21,"tag":53,"props":54,"children":55},"ul",{},[56,62,67],{"type":21,"tag":57,"props":58,"children":59},"li",{},[60],{"type":27,"value":61},"Ensure browsers are up to date.",{"type":21,"tag":57,"props":63,"children":64},{},[65],{"type":27,"value":66},"Verify any software accessing GitHub uses modern TLS implementations.",{"type":21,"tag":57,"props":68,"children":69},{},[70],{"type":27,"value":71},"Monitor for updates from GitHub regarding the transition timeline.",{"type":21,"tag":30,"props":73,"children":74},{},[75],{"type":27,"value":76},"This proactive shift enhances security across GitHub’s infrastructure, aligning with industry best practices in cryptographic safety.",{"title":7,"searchDepth":78,"depth":78,"links":79},2,[80,81,82],{"id":24,"depth":78,"text":28},{"id":37,"depth":78,"text":40},{"id":48,"depth":78,"text":51},"markdown","content:blog:sunsetting-sha-1-in-https-on-github.md","content","blog/sunsetting-sha-1-in-https-on-github.md","blog/sunsetting-sha-1-in-https-on-github","md",1776928761272]