Slashdot Mirror


Mozilla Accepts Chinese CNNIC Root CA Certificate

Josh Triplett writes "Last October, Mozilla accepted the China Internet Network Information Center as a trusted CA root (Bugzilla entry). This affects Firefox, Thunderbird, and other products built on Mozilla technologies. The standard period for discussion passed without comment, and Mozilla accepted CNNIC based on the results of a formal audit. Commenters in the bug report and the associated discussion have presented evidence that the Chinese government controls CNNIC, and surfaced claims of malware production and distribution and previous man-in-the-middle attacks in China via their secondary CA root from Entrust. As usual, please refrain from blindly chiming into the discussion without supporting evidence. Since Mozilla has already accepted CNNIC as a trusted root CA, the burden rests with those who argue for its removal."

36 of 256 comments (clear)

  1. As usual, please refrain from blindly chiming in? by gad_zuki! · · Score: 5, Funny

    Wow, youre so new here, youre still dripping wet and covered in placenta.

  2. Given they've bowed to Chinese pressure by sethstorm · · Score: 4, Interesting

    ...is there a straightforward way to mark CNNIC as untrusted?

    --
    Twitter supports and protects racists - by smearing their critics with the "Hate Speech" label.
    1. Re:Given they've bowed to Chinese pressure by Zocalo · · Score: 4, Informative

      You could just delete the certificate yourself. "Edit, Preferences, Advanced, Encryption, View Certificates"[1]. Select the one from CNNIC and hit "Delete".

      [1] "Tools, Options, Advanced, Advanced, View Certificates" if you are on Windows, but if you are on Windows the CNNIC certificate is probably not the most significant of your security worries... :)

      --
      UNIX? They're not even circumcised! Savages!
    2. Re:Given they've bowed to Chinese pressure by data2 · · Score: 3, Funny

      Edit -> Preferences -> Advanced -> Encryption -> View Certificates -> Authorities -> ... -> Profit

  3. Marking as untrusted by Saishuuheiki · · Score: 5, Informative

    Taken from comments section of article:

    Individual CAs can be removed via the "advanced" preferences panel. It's instructive, actually, to look at the list - there's a lot of entries there.

    One could switch to another browser, but it's worth thinking about how open that browser's CA inclusion process is first.

  4. Was pointing towards something like a CRL. by sethstorm · · Score: 3, Insightful

    Removing it is fine until an update/reinstall brings it back. Telling the browser to not trust that entity at all is what I'm talking about.

    --
    Twitter supports and protects racists - by smearing their critics with the "Hate Speech" label.
    1. Re:Was pointing towards something like a CRL. by micheas · · Score: 3, Insightful

      Removing it is fine until an update/reinstall brings it back. Telling the browser to not trust that entity at all is what I'm talking about.

      As long as the update does not delete your local preferences it should work.

    2. Re:Was pointing towards something like a CRL. by Sir_Lewk · · Score: 3, Insightful

      Ah, but how do we know we are actually getting the right extension? Normally that process is secured by ssl but now.... The Chinese government could man in the middle anyone who tries to install any particular extension, and feed them a crippled one instead. Implausible sure, but possible.

      --
      "linux is just DOS with a UNIX like syntax" -- Galactic Dominator (944134)
    3. Re:Was pointing towards something like a CRL. by Minwee · · Score: 3, Informative

      Select "Tools", then "Options".

      Click "Advanced", "Encryption" and "View Certificates".

      Scroll down to "CNNIC" and select the "CNNIC Root" certificate.

      Finally click "Edit", uncheck "This certificate can identify web sites" and press OK until all the little windows go away.

      Now even if the root certs are updated, that cert remains untrusted.

      In IE you have to select "Tools", "Internet Options", "Content", "Certificates", "Trusted Root Certification Authorities", select the certificate you want, then click "Advanced", uncheck the "Server Authentication" role and then click "Ok", "Close", and "OK" again to finally make your change stick.

      What is ironic is that when you do that in IE with no problems, it actually takes more mouse clicks than doing the same thing in Firefox.

    4. Re:Was pointing towards something like a CRL. by FreelanceWizard · · Score: 3, Interesting

      This will work, but the certificate is still "trusted" in a sense. The best way is, as the parent noted, to use the Certificates snap-in in MMC to move the certificate to the Untrusted store. Doing so permanently removes trust for that certificate and, thus, all of the certificates that chain to it. This approach is also useful in that it blocks trust of the certificate for any purpose by any program that uses the cryptographic functions in Windows for verifying certificate trust.

      --
      The Freelance Wizard
  5. You're kidding, right? by taoye · · Score: 5, Funny

    Just wait while I go infiltrate the Chinese government to determine if they are doing bad things through CNNIC, so I can come back with evidence. While I'm at it, I'll be travelling through West Africa and I have the sum of $1,000,000,000 USD of money stashed there and I need your help to get it out of the country. I will give you 10% guaranteed.....

  6. Disagree with the premise. by Jane+Q.+Public · · Score: 5, Interesting

    "Since Mozilla has already accepted CNNIC as a trusted root CA, the burden rests with those who argue for its removal."

    I am not sure I agree with this. When accepting something that is very controversial, like for example accepting CNNIC as a neutral authority, or backing a perpetual-motion technology, the burden may very well be on the actor to defend its actions.

  7. delete cert? finger in dike by Onymous+Coward · · Score: 4, Informative

    Did you notice how many CAs are in the list? How do you feel about each?

    I might recommend encouraging technologies like Perspectives to provide defense in depth.

    1. Re:delete cert? finger in dike by zonky · · Score: 4, Informative

      Sound advice. For those new to perspectives, it uses notary servers, and compares the thumbprint of the SSL cert with what 4-5 other points on the internet see. This should at least prevent localised MITM, even with a trusted CA issuing the MITM cert.

    2. Re:delete cert? finger in dike by Onymous+Coward · · Score: 4, Informative

      They've got a Firefox extension, too: http://www.cs.cmu.edu/~perspectives/firefox.html#install

      And this conveys the idea quickly and visually... the web demo: http://moo.cmcl.cs.cmu.edu/perspectives/

      They're also looking for developers to take the project. This could be a great tool for everyone.

  8. Re: As usual, please refrain from blindly chiming by Actually,+I+do+RTFA · · Score: 5, Insightful

    I take issue to the next phrase: "Since Mozilla has already accepted CNNIC as a trusted root CA, the burden rests with those who argue for its removal."

    Are you saying "should Mozilla remove it?" Then the answer is probably no, becuase Mozillia is not an omni-beneficent entity. It probably helps them in some way to include it.

    The question is, should individual users remove it? And yes, by the link that you provided indicating it's role in the distribution of malware. Why should I let Mozilla, a large group with contradictory desires and many masters, control whether I delist it as a trusted root?

    --
    Your ad here. Ask me how!
  9. Re: As usual, please refrain from blindly chiming by TSHTF · · Score: 4, Informative

    Opera trusts CNNIC also.

  10. Relative security of self-signed certificates by Anonymous Coward · · Score: 4, Insightful

    I have nothing against additional certificate authorities; it makes sense in most situations not to give all the power to a single party.

    Nonetheless, the large number of accepted authorities raises serious questions about another aspect of browser security:

    Why are self-signed certificates viewed with such relative suspicion?

    It only takes a single compromised or misled CA to bypass the entire trust system. The more CAs we have, the easier it is to compromise the system.

    Why, then, do we make it so difficult for sites to implement security against passive plaintext snooping (which is arguably much more of a threat in most situations, discounting targeted attacks)? Why do browsers make this basic security effectively unavailable unless you pay a toll to a CA? (And it is effectively unavailable, since the inconvenience and fear-of-the-unknown related to accepting self-signed certificates makes the use of them a self-defeating act.)

    As CAs proliferate, it becomes more and more meaningless to view self-signed certificates with such suspicion -- since they become relatively less and less of a risk, as we add more CAs and thus more individual points where the system may be compromised.

    1. Re:Relative security of self-signed certificates by marcansoft · · Score: 3, Insightful

      So when Joe Haxor manages to use a cheap DNS exploit to point www.mybank.com to his web server and then hands out a self-signed certificate 'proving' it's www.mybank.com, you really think that not having a padlock icon on the window will stop Joe Average from handing over their passwords and thereby all their money?

      Joe Haxor will use a cheap DNS exploit to point www.mybank.com to his web server, which will not support, enable, or redirect to HTTPS. Or do you really believe that Joe Average actually types https://www.mybank.com? You're lucky if they even get the www. part in.

      Sorry, self-signed certs are better than than unencrypted HTTP, and unconditional roadblocks to their use are ridiculous when anyone can impersonate anyone over simple unencrypted HTTP. Anyone can argue that they should not be given equivalent security status to CA certificates (and I agree), but actively hindering their use is stupid and actively hurts security by discouraging Joe Web Developer from trivially enabling SSL to at least stop passive snooping.

  11. Does anyone notable *not* support CNNIC? by RalphBNumbers · · Score: 4, Informative

    I just checked, and both MacOS X and Windows 7 seem to trust the CNNIC root...

    If this is really a problem, and I haven't the slightest idea if it is, then it extends way beyond firefox.

    --
    "The worst tyrannies were the ones where a governance required its own logic on every embedded node." - Vernor Vinge
    1. Re:Does anyone notable *not* support CNNIC? by iammani · · Score: 3, Informative

      Chrome does not.

    2. Re:Does anyone notable *not* support CNNIC? by dunng808 · · Score: 3, Insightful

      > ... it extends way beyond firefox.

      And it extends way beyond China. I see this as simply another example of "yellow peril" thinking. What about the Brits, who want to monitor everything? What about the French, who want to kick people off the net for misbehaving? What about Iran, who wants to kick out everyone? Do you really think the USA looks like the good guys to the rest of the 'net? Who gave the world Microsoft, and the RIAA, and the MPAA? All this "evil Chinese" stuff is getting tiresome.

      --

      Gary Dunn
      Open Slate Project

    3. Re:Does anyone notable *not* support CNNIC? by ScrewMaster · · Score: 3, Insightful

      > ... it extends way beyond firefox.

      And it extends way beyond China. I see this as simply another example of "yellow peril" thinking. What about the Brits, who want to monitor everything? What about the French, who want to kick people off the net for misbehaving? What about Iran, who wants to kick out everyone? Do you really think the USA looks like the good guys to the rest of the 'net? Who gave the world Microsoft, and the RIAA, and the MPAA? All this "evil Chinese" stuff is getting tiresome.

      Gagh. Such histrionics. Look, this isn't about all Chinese people being evil. It is about a particular country that happens to be the source of an astounding number of remote attacks, cracks, hacks and exploits on the network infrastructure of other nations. The question is whether or not those nations who are subject to China's self-serving Internet activities should aid in those efforts. Rather a foot-in-self-shoot situation really. Me, I've all but switched to Chrome anyway for most things, and this is just another reason to finish the job.

      I know what you're saying when you use the phrase "yellow peril", but there is some truth to it. China is a threat on the world scene, more than at any other point in their history.

      --
      The higher the technology, the sharper that two-edged sword.
  12. Re: As usual, please refrain from blindly chiming by gd2shoe · · Score: 5, Insightful

    At issue here is the ability of the Chinese government to run MiTH attacks on their citizens (and others) (who may have no computer security experience) and to arrest political dissidents. Nobody's saying you should wait to remove it. The question is, should it be removed for the safety of others?

    The whole point of root certs is trust. We trust them to sign certificates which will be used, in turn, to keep our conversations private. Should CNNIC be trusted to keep conversations private? That is the question. Organizations like Mozilla put their own reputations on the line when choosing which root certs to include. Any abuse by CNNIC will be seen as a security flaw in Mozilla software. That is the issue. That is why Mozilla should care. (even if they disagree)

    --
    I won't join Slashcott. OTOH, If Beta goes live, I just won't be back until it's fixed. Sorry Dice.
  13. Evidence by Spy+Hunter · · Score: 5, Insightful

    It would be easy enough to prove that CNNIC is performing man-in-the-middle attacks. To perform a man-in-the-middle attack on (for example) gmail, CNNIC would have to send a fraudulent certificate to users. That certificate would be ironclad evidence that CNNIC can't be trusted, so all someone has to do is present one.

    --
    main(c,r){for(r=32;r;) printf(++c>31?c=!r--,"\n":c<r?" ":~c&r?" `":" #");}
  14. Something more substantial than Wikipedia ? by Antiocheian · · Score: 5, Interesting

    "surfaced claims of malware production and distribution"

    This claim cites Wikipedia and in particular this unverifiable, POV-ridden paragraph:

    "CNNIC produces one of the best-known malwares in China: the Chinese-Language-Surfing Official Edition(). The software is frequently bundled with other adware/sharewares. It was declared malware by Beijing Network Industry Association() and San Ji Wu Xian Co Ltd., the company behind 360 Safeguard(360), an anti-virus software. San Ji Wu Xian was sued by CNNIC for 150,000 RMB and the court ruled out favorably towards CNNIC."

    Which libels CNNIC for connections with malware while the only case against CNNIC was actually ruled towards their favor.

    Why is CNNIC untrustworthy ? In plain English please.

    1. Re:Something more substantial than Wikipedia ? by brennz · · Score: 3, Interesting

      Are you saying the court system in China is (A) open, fair, and impartial, particularly when it judges a case involving (B) the Chinese Govt vs a defendant anti-spyware company?

    2. Re:Something more substantial than Wikipedia ? by Jeremy+Erwin · · Score: 4, Insightful

      San Ji Wu Xian was sued by CNNIC for 150,000 RMB and the court ruled out favorably towards CNNIC.

      Tell me why I should trust a Chinese court. Because the Chinese Communist Party tells me they're trustworthy? Sorry, I'm not sure I should trust the CCP. Can you provide a trustworthy source that will attest to the CCP's ethics?

  15. Re: As usual, please refrain from blindly chiming by Anonymous Coward · · Score: 4, Insightful

    If only we had the luxury of knowing which certificates to remove if you didn't trust the NSA. Guess MITM is a game for big players.
    Our instructions for setting up VPN include a recommended step where you disable all root certificates but one for the connection. From a security standpoint, the whole web should work the same.

    It's very annoying how Firefox insists on making self-signed certificates the biggest pain in the ass possible to accept, knowing you can't really trust the 'trusted' signers in the first place. For forums and the likes, just permanently storing the certificate so you can be sure you're getting an encrypted connection to the same entity each time would be sufficient.

  16. Re: As usual, please refrain from blindly chiming by bill_mcgonigle · · Score: 3, Informative

    He means, "please don't spam the Bugzilla comments unless you have something constructive to add." BMO used to block all slashdot referers at one point...

    --
    My God, it's Full of Source!
    OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
  17. Re: As usual, please refrain from blindly chiming by Anonymous Coward · · Score: 3, Funny

    What's a MiTH attack? Man in ..?

    Man in The Hat

  18. Re:restricting it to *.cn would make sense by ScrewMaster · · Score: 4, Interesting

    Seeing as China makes lots of the core internet routers these days (with quickly growing market share) there is every reason to assume we're getting man-in-the-middle pwned.

    I'm not in *.cn, and I'm not visiting *.cn, so why in Hell should this certificate apply to me? If suddenly www.adobe.com is signed by China, there sure is a problem!

    It's funny, you know ... if we were all buying high-end routers from Russia everyone would flipping out about security. But China makes inroads on that market (with the obvious intention of dominating it) and nobody really seems too upset. You have to assume that a hostile totalitarian state might try to exploit that advantage in some way.

    Weird. And I always thought denial was a river.

    --
    The higher the technology, the sharper that two-edged sword.
  19. I'm sorry sir, the certificate is in Chinese by syousef · · Score: 4, Funny

    Why is CNNIC untrustworthy ? In plain English please.

    I'm sorry sir, the certificate is in Chinese.

    --
    These posts express my own personal views, not those of my employer
  20. Re:Why bother, there's always opera by BZ · · Score: 3, Informative

    Of course Opera also trusts this CA. But yes, there's always Opera. ;)

  21. Re: As usual, please refrain from blindly chiming by elronxenu · · Score: 3, Insightful

    Not only do I not trust CNNIC, I don't trust Verisign either. Nor any of the dozens of CAs which are installed by default.

    In other words, the whole CA concept is flawed.

  22. Re: As usual, please refrain from blindly chiming by u38cg · · Score: 3, Interesting

    Not if it continues to be signed back to a root, which is the point. A previous employer of mine had its own root cert in our (IE6) browsers and I only noticed after a similar, related discussion on Slashdot caused me to look. I removed it temporarily and yep, all https traffic was being MITM'd. Given the nature of the organisation, it was understandable that they had to be able to audit such traffic, but that doesn't excuse them not talking about it. I later mentioned it to a 2nd line tech who was doing something unrelated and it was news to him, too.

    --
    [FUCK BETA]