GitHub 要求全面檢查 SSH Key

GitHub 被攻擊成功後 (參考 GitHub 官方所說的「Public Key Security Vulnerability and Mitigation」這篇),官方除了把漏洞修補完以外,接下來做了更積極的措施:暫停所有的 SSH key 存取權限,一律等到用戶 audit 確認過後才開放:「SSH Key Audit」。

這次 GitHub 除了修正問題、audit key 以外,另外還提出了新的機制讓用戶更容易發現異常存取行為,包括了:

  • 新增 SSH public key 時要輸入密碼。
  • 新增 SSH public key 成功後會寄信通知。
  • 新增「Security History」頁面可以看到帳戶的安全狀況。

算是很積極補救的作法。

另外說明,要如何 audit key,也就是要如何取得你的 public key fingerprint:

ssh-keygen -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 with read permissions, and clone/pull/push access to repositories with write permissions. As 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 or more SSH 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.

# Status

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 any time a 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 support@github.com

把 GitHub 上的 private repository 搬到 BitBucket 上...

既然 latency 都差不多 (兩個 site 從台灣過去都要 200ms),git push 速度感覺起來也差不多,找不到理由要付錢給 GitHub,加上 private repository 裡面也沒什麼特別的東西,剛剛就都改丟到 BitBucket 上面,然後把 GitHub 的付費機制 cancel 掉...

步驟很簡單,在 BitBucket 上開好 private repository,然後把 .git/config 裡面的 origin 換掉後重新 git push -v origin master 就好了。

參考:

GitHub 今天晚上在台北有聚會!

GitHub 剛剛發信給地址裡有「Taipei」的人,通知大家晚上在台北有聚會... 但是看到信件的時候已經是下午兩點 XD

這是 blog 上的公告:「Taipei Drinkup Tonight!」。(不,天氣太冷了,我要在棉被裡面找周公)

直接借地圖來用:(在「Juliana食尚餐飲運動酒吧」)

有興趣的人可以去聊聊...

GitHub 的 DMCA 政策

GitHub 是美國公司,所以會受到 DMCA 的影響,前幾天他們公佈了收到 DMCA Takedown 時的政策與作法:「DMCA Takedown」(話說回來,help.github.com 居然沒有上 HTTPS)。

然後很有 GitHub 風格的開了一個 repository 來管這些 Takedown Notice (噴茶):「https://github.com/github/dmca」,目前已經看到兩封了,以後應該可以看到很多「範本」。其中一封是 Sony 針對 PS3 破解工具發 Takedown notice:「2011-01-27-sony.markdown」(Slashdot 的報導在「Sony Sends DMCA Takedown Notice To GitHub」)

另外一個有公開 Takedown notice 的是 The Pirate Bay,參考「Legal threats against The Pirate Bay」,這邊也有很多範本 XD (應該是只刊出大公司的 XD)