3 ms·
... and what feature of any Javascript browser crypto makes it anything more than trivial to defeat by such an attacker? You can use sslstrip or malicious trus
by marshray 15y ago
... and what feature of any Javascript browser crypto makes it anything more than trivial to defeat by such an attacker?
You can use sslstrip or malicious trusted CAs to argue the imperfection of SSL/TLS as deployed by browsers and users, but it does not follow that that somehow makes Javascript browser crypto any less broken.
- tptacek 15y agosslstrip is also in large part a solved problem. There are definitely major problems with HTTPS/TLS as a security system, but I think most of them are UI/UX issues. What that means is we get a choice: * Rebuild everything from scratch and spend 15+ years testing it back into reliability, or * Rebuild just the UX for a protocol we otherwise known to be sound.
- magikarp 15y agoI don't understand why a protocol with known major problems that can be compromised by oppressive governments is a better solution to client-side crypto that can be verified for integrity and hides the plaintext from the server.
- jbri 15y agoTLS encryption can't be compromised by oppressive goverments. Only the CA-based authentication can. Trying to "fix" this by rolling your own ad-hoc encryption (while ignoring the authentication issue entirely) is completely missing the point.
- tptacek 15y agoOnly the configuration of the CA-based authentication can. Nobody loves X509 PKIs, but so far, they seem to "work". This matters because you can literally write a HOWTO that my mom could follow to get a browser configured so that China can't snoop on (many of) your HTTPS connections. No code required.
- tptacek 15y agoThe protocol doesn't have known major problems.