News for hackers. Stuff that matters.
Re:No, don't enable revocation checking by higherpurpose on Sunday April 20, 2014 @04:53AM (#7616278)
From Moxie:

"Convergence is blocking on TACK, which is blocking on browser vendors."

https://twitter.com/moxie/status/451020203099299840

Re:No, don't enable revocation checking by ivanr on Sunday April 20, 2014 @05:23AM (#7616328)
There should be a clear statement about the status of Convergence on the web site. IIRC, the Firefox extension has been broken for more than a year now. Why? If Mozilla broke their APIs and made it impossible for the extension to work, then we should know about that. Otherwise, what's the excuse for the extension being broken for so long?

Convergence had the momentum, and there was a small but vocal group of people willing to support it. But, due to project mismanagement and lack of communication, that momentum has been lost.

Re:No, don't enable revocation checking by 0x006A on Sunday April 20, 2014 @05:57AM (#7616371)
There are some more active forks like https://github.com/mk-fg/convergence/ but they too seam to not really work in current versions of Firefox.
Re:No, don't enable revocation checking by y0ghur7_xxx on Sunday April 20, 2014 @06:35AM (#7616417)
I don't understand this. Can someone weight in with an explanation? Convergence works just fine without TACK: I can set up two or more notaries on some VPS somewhere, and my browser would check if the notaries see the same certificate on that server I am trying to connect to as my browser. Seems secure to me: no external CA involved, the certificate on the web server can be self signed, and a MITM attack would need to hack two or more external servers to be successful. How does TACK fit in all of this?