Re: Convergence.
Aymeric Vitte <[email protected]> Tue, 15 Apr 2014 19:22:36 +0200
| Newsgroups | gmane.comp.mozilla.devel.security.policy,gmane.comp.mozilla.security,gmane.comp.mozilla.devel.plugins,gmane.comp.mozilla.wishlist |
|---|---|
| Message-ID | <[email protected]> |
I did not look again but as far as I remember the concepts of convergence are not really applicable any longer, because they suppose that there is a finite set of certificates used, and if you look at sites like google, twitter, etc with some plugins to catch the certificates, you will see that they keep their time changing certificates, and for some they can issue them by themselves. I don't know why they are doing this but then you have really no way to know to whom you are talking to from the user perspective, http pinning is more protecting the sites than the users. I don't know about the "Certificate transparency" standard but I don't see very well how this could help given the above remark. Regards Aymeric -- Peersm : http://www.peersm.com node-Tor : https://www.github.com/Ayms/node-Tor GitHub : https://www.github.com/Ayms Le 15/04/2014 18:08, Daniel Veditz a écrit : > On 4/15/2014 7:43 AM, nobody wrote: >> I just wondered... what is the pull back regarding Convergence to put >> it in >> the webbrowsers by default? > > The main issue is who are the notaries? If they're simply reflecting > back "Yup, I see this valid CA cert" then they aren't adding a whole > lot of value for the amount of risk they introduce, and if they're > making their own judgement about the validity of the certificates on > some other ground they just become a type of Certificate Authority > themselves. Who pays for that infrastructure, and what is their motive? > > Firefox and Chrome are both working on implementing "key pinning" (and > participating in the standardization process for it) which won't "free > us from the CA system" but will at least ameliorate one of the worst > aspects which is that any two-bit CA anywhere in the world can issue a > certificate for any site, anywhere. > > The IETF is working on standardizing "Certificate Transparency", > Chrome is implementing it, and at least one CA is participating. This > again doesn't free us from the CA system, but it does make the public > certificates auditable so that mis-issuance could theoretically be > detected. > >> Or I hack the router you >> use to access the internet... all of the notaries you try to >> talk to I >> redirect to me. I say every site is >> valid regardless if it is or not. How is this more secure? > > I haven't looked at the technical details of convergence but > presumably it requires a secure connection to the notary or better > that the notary responses are signed by the notary. If the > communication with the notary is unreliable then it's no help at all. > > The main practical problems with convergence are that it introduces a > dependency on traffic to a 3rd party which hurts privacy, reliability, > and performance. These are similar to the problems we have today with > OCSP revocation checking. > > -Dan Veditz > _______________________________________________ > dev-security mailing list > dev-security-CzyLcWPZiU5YsZ3hbOqMTti2O/[email protected] > https://lists.mozilla.org/listinfo/dev-security