<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ssh-Security on CuraDevOps</title><link>https://curadevops.metacog.co.kr/tags/ssh-security/</link><description>Recent content in Ssh-Security on CuraDevOps</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 23 Sep 2026 15:14:55 +0000</lastBuildDate><atom:link href="https://curadevops.metacog.co.kr/tags/ssh-security/index.xml" rel="self" type="application/rss+xml"/><item><title>GitHub removing legacy SSH algorithms, requiring larger RSA keys</title><link>https://curadevops.metacog.co.kr/insights/2026-09-23-security-improvements-for-ssh/</link><pubDate>Wed, 23 Sep 2026 15:14:55 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-09-23-security-improvements-for-ssh/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Plan:&lt;/strong> Review any SSH keys used for infrastructure automation against GitHub repos (deploy keys, Ansible/Terraform git sources) to confirm they meet the new algorithm and minimum RSA key-size requirements before the removals take effect; no hard deadline is published yet.&lt;/li>
&lt;li>&lt;strong>CI/CD — Plan:&lt;/strong> Audit SSH deploy keys and runner SSH credentials used to pull private repos or push artifacts via GitHub to ensure they use accepted algorithms and sufficiently large RSA keys; schedule rotation for any that don&amp;rsquo;t comply before the removal lands.&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;/ul></description></item></channel></rss>