We updated our RSA SSH host key
The fact that this key was apparently not stored in an HSM, and that GH employees had access to this private key (allowing them to accidentally push it) means that effectively all communication with GH since the founding of the company has to be considered compromised.  This basically means that, depending on your level of paranoia, you will have to review <i>all</i> code that has <i>ever</i> interacted with Github repositories, and any code pushed or pulled from private repositories can no longer be considered private.<p>Github&#x27;s customers trust GH&#x2F;MS with their code, which, for most businesses, is a high value asset. It wouldn&#x27;t surprise me if this all results in a massive lawsuit. Not just against GH as a company, but also to those involved (like the CISO). Also, how on earth was it never discovered during an audit that the SSH private key was plain text and accessible? How has GH ever been able to become ISO certified last year [0], when they didn&#x27;t even place their keys in a HSM?<p>Obviously, as a paying customer I am quite angry with GH right now. So I might be overreacting when I write this, but IMO the responsible persons (not talking about the poor dev that pushed the key, but the managers, CISO, auditors, etc.) should be fined, and&#x2F;or lose their license.<p>[0] <a href="https:&#x2F;&#x2F;github.blog&#x2F;2022-05-16-github-achieves-iso-iec-270012013-certification&#x2F;" rel="nofollow">https:&#x2F;&#x2F;github.blog&#x2F;2022-05-16-github-achieves-iso-iec-27001...</a>