在「Mozilla 在考慮移除 WoSign 的 CA Root」這邊提到的事情，隨著時間的發展，大家發現事情愈來愈誇張。
在兩個小時前 Mozilla 的 Gervase Markham 提出了對 WoSign + StartCom 處置的草稿：「WoSign and StartCom」，草稿在 Google Docs 上的「WoSign and StartCom」這邊可以看到。另外 Mozilla 在 wiki 上「CA:WoSign Issues」將 WoSign + StartCom 的事情都整理了出來，也是重要的資料。
文章很長，先講結論：目前 Mozilla 打算把 WoSign 與 StartCom 所簽出的 certificate 都照當年 CNNIC 的方式拔掉。
從頭說明，事情發生於八月底的時候 Google 通知了 Mozilla 一連串 WoSign 出包卻沒有主動通報的事件，當時知道的大約有三或四件。而在 mozilla.dev.security.policy 不斷的討論的情況下，由於關注度變得超高，在搜尋大量的資料下發現更多問題，到現在 Mozilla 的 wiki 上已經列出了 13 個。
而這邊以 Mozilla 最後整理的草稿，將 13 個事件整合起來成幾件來說明：
WoSign and Back-Dated SHA-1
在瀏覽器會對 2016 後所簽出直接跳 error 的情況下 (像是「An update on SHA-1 certificates in Chrome」)，直接偽造是 2015 年簽出的 certificate。
WoSign’s Ownership of StartCom
Mozilla 的 CA program 要求當公司擁有權轉移時必須揭露：
[...], Mozilla’s program requirements say that a change of CA ownership must be disclosed. In this case, that was not done - and in fact, the change was directly denied a few months after it happened.
直到最近被抓到而揭露後，發現 WoSign 所揭露的也不正確，StartCom 已經開始使用 WoSign 的 infrastructure 了：
More recently, even after the evidence of total control was public, WoSign referred to their interest in StartCom in a press release as “an equity investment”, and maintain that the two businesses continue to be separate even today. They say “the original system ... of StartCom remains unchanged”.
However, there is technical evidence that around a month and a half after the acquisition, StartCom issuances switched to using WoSign’s infrastructure - either the same instance of it, or their own instance.
而 Mozilla 要求 WoSign 提供他們產生 serial number 的程式碼時：(在 WoSign 簽出重複的 serial number 問題時得到的)
Mozilla asked WoSign how they generated their serial numbers, and was told that they used the Java package java.crypto.SecureRandom. They supplied the following code snippet:
However, as can be seen from this simple test harness, this code snippet does not produce serial numbers matching WoSign’s idiosyncratic pattern.
再度發現 WoSign 給的程式碼對不上。(hey)
然後再多方面分析後發現 WoSign 宣稱跟 StartCom 只共用 CRL/OCSP (revoke 機制) 是假的。Mozilla 由多方面判斷發現，至少程式碼是共用的 (i.e. clone)，甚至猜測整個系統都是共用的 (在更後面提到)：
We believe that, taken together, all this shows that StartCom’s certificates are now being issued using either WoSign’s existing infrastructure or a clone of it, and that WoSign’s operational control of StartCom began straight after the November 1st 2015 sale date. This evidence should be compared against WoSign’s recent assertion that “Even now, it still independent in the system, in the validation team and management team, we share the CRL/OCSP distribution resource only.”
SHA-1 Exceptions Process
再來是講一些背景。因為金流產業到了 2016 年還是有系統不支援 SHA-256 certificate，而 CA/Browser Forum 已經禁止簽發 SHA-1 憑證了，所以 2016 年二月的時候 WorldPay 跑上來尋求例外：
This became clear in February of 2016, where a payment processor called WorldPay applied to the CAB Forum for an exception so they could acquire 8 SHA-1 certificates to keep SSL working for their legacy payment terminals. Their CA was unable to help them because of the ban in the CAB Forum Baseline Requirements, and to issue in violation of the ban would lead to a “qualified” (not clean) audit, which might lead to browsers no longer accepting their audit as valid to keep them trusted.
而在亞利桑那的 face-to-face meeting 中剛好就討論了這點，允許 Symantec 簽發，而要提出來的是，WoSign 的 Richard Wang 也在場：
This issue was discussed at length in the CAB Forum face-to-face meeting from 16th-18th February 2016 in Scottsdale, Arizona (where Richard Wang of WoSign was present). Mozilla then had a public discussion about it in our policy forum starting on 23rd of February. In the end, the browsers reluctantly agreed to let Symantec issue these certificates for Worldpay - or rather, they agreed to accept that Symantec’s next audit would be qualified in this way.
所以 Mozilla 再次強調，當下大家的結論是特別許可，簽發被禁止的 SHA-1 certificate 是很嚴重違反規定的事情：
Even at this point, in February 2016, it was (or should have been) clear to all CAs, including WoSign, that issuing SHA-1 certificates in violation of the ban was a Very Big Deal, and that permission had to be sought from the browsers in order for the CA not to face difficulty.
|Feb 3rd 2010||GeoTrust issues a SHA-1 certificate for *.tyro.com from their Equifax root, valid until May 6th 2013.|
|Apr 6th 2013||A month before their old cert expires, GeoTrust issues a replacement SHA-1 certificate for *.tyro.com from a GeoTrust root, valid until June 7th 2016. A simple roll-over replacement.|
|Jan 1st 2016||SHA-1 issuance ban comes into effect.|
|May 24th 2016||A month before their old cert expires, GeoTrust issues a SHA-256 certificate for *.tyro.com from a GeoTrust root, valid until June 23rd 2019.|
但 Tyro 在 2016 年五月拿到的 SHA-256 憑證很明顯不合用，於是試著找 SHA-1 憑證... 結果不管怎樣，後來拿到了 StartCom 所簽出來的 SHA-1 憑證，而藉由技術上的 pattern 可以發現這是 back-dated (偽造日期簽發)：
But the strong evidence is that this SHA-256 certificate did not meet Tyro’s needs. We can see a SHA-1 certificate for *.tyro.com which was logged in CT on June 8th 2016, a day after their previous SHA-1 certificate expired. This certificate is not issued by GeoTrust (who still provide the cert for their main website) or Comodo, tyro.com’s usual providers, but by StartCom. And the notBefore date is that magic date of 20th December, 2015 - a date on which, as noted above, StartSSL.com was closed for upgrading, and on which we have seen many Macau certificates issued by WoSign, which we believe are back-dated.
The SHA-1 certificate in question is still in use today on https://iclient.tyro.com/.
最後 Mozilla 得到的結論：
- StartCom are using WoSign’s infrastructure (the same or a clone);
- Certificates on this infrastructure with a notBefore of 2015-12-20 (China time) are indeed back-dated - this further confirms our suspicions about the Macau certificates we saw issued by WoSign; and
- StartCom’s hierarchy has been directed by management to mis-issue “WoSign-style”.
同時他們認為最後一點是最嚴重的一點，你必須將 StartCom 視為與 WoSign 完全同樣的公司，所有對 WoSign 的檢查與處置都必須相同對應到 StartCom 上：
This last point is important; the practices at WoSign are now being seen at StartCom. Therefore, we conclude that all of ownership, infrastructure and control are sufficiently common between the two companies that it would therefore be reasonable for any action Mozilla chooses to take against WoSign to also be taken against StartCom and vice versa.
另外一個很嚴肅的問題，CA 架構是建立在稽核機制上，而 WoSign 所選擇的稽核單位無法稽核出應有的「多個問題」：
WoSign’s auditors, Ernst & Young (Hong Kong), have failed to detect multiple issues they should have detected. (Issue J, Issue X)
提案的處理方式類似於 CNNIC 當時被拔掉的方式，針對某個日期之後的都不信任。這同時包括了 WoSign 與 StartCom 的 certificate。這真是可喜可賀啊...