这次 GitHub 除了修正问题、audit key 以外，另外还提出了新的机制让用户更容易发现异常存取行為，包括了：
算是狠积极补救的作法。另外说明，要如何 audit key，也就是要如何取得你的 public key fingerprint：
-lf .ssh/id_rsa.pub (如果你是用 RSA) 或是 ssh-keygen -lf .ssh/id_dsa.pub (如果你是用 DSA)
出现的讯息就是你要比对的值。记住！既然是 audit，请一个一个比对确认 fingerprint 全部都正确。
附上原始信件：(好像还没在 blog 上说明)
A security vulnerability was recently discovered that made it possible for an attacker to add new SSH keys to arbitrary GitHub user accounts. This would have provided an attacker with clone/pull access to repositories withpermissions, and clone/pull/push access to repositories with permissions. of 5:53 PM UTC on Sunday, March 4th the vulnerability no longer exists.
While no known malicious activity has been reported, we are taking additional precautions by forcing an audit of all existing SSH keys.
# Required Action
Since you have one orSSH keys associated with your GitHub account you must visit https://github.com/settings/ssh/audit to approve each valid SSH key.
Until you have approved your SSH keys, you will be unable to clone/pull/push your repositories over SSH.
We take security seriously and recognize this never should have happened. In addition to a full code audit, we have taken the following measures to enhance the security of your account:
- We are forcing an audit of all existing SSH keys
- Adding a new SSH key will now prompt for your password
- We will now email you anya new SSH key is added to your account
- You now have access to a log of account changes in your Account Settings page
Sincerely, The GitHub Team
— https://github.com email@example.com