Re:WebRTC is almost here, and it will change the web
by msutherl on Monday August 13, 2012 @08:21PM
(#4378824)
Don't make the mistake of thinking that because the communication channel is "encrypted", it is secure. SSL can already be compromised (so much for trusting encrypted transport) and the WebRTC client code could be compromised (always a problem).
[ Parent
| on HN ]
Re:WebRTC is almost here, and it will change the web
by Egregore on Tuesday August 14, 2012 @04:29AM
(#4379951)
Can you please provide links on how SSL can be compromised?
Re:WebRTC is almost here, and it will change the web
by rmc on Tuesday August 14, 2012 @05:17AM
(#4380035)
It's not SSL per se, but the Certification Authority system that is weak. If you get one of the root CA certs, you can make any SSL cert a valid SSL cert for any domain name.
Re:WebRTC is almost here, and it will change the web
by Egregore on Tuesday August 14, 2012 @08:03AM
(#4380451)
It's correct that if root CA is compromised you can make fakes.
To protect against this attack browsers should warn when certificate changes, there even is a long standing bug for firefox in mozilla:
Re:WebRTC is almost here, and it will change the web
by nuje on Tuesday August 14, 2012 @07:59AM
(#4380435)
The fact that you can bungle WebRTC or SSL/TLS implementation doesn't make it useless for transport security. But of course
security building blocks never guarantee properties of
the entire system alone. Just like using AES doesn't make or break your security.