Title says it all. It's ok that these browsers on Nokia decrypt HTTPS, because they need to for proxy-proxy... but I mean, then inform your users about it.
I don't understand the technical side of all this, but what really bothers me is that these parties can decrypt data sent over https. Doesn't that mean that https is not secure and that it's a waste of time?
No. The decryption is necessary if you want proxy-compression of HTTPS requests. Opera Mini is a proxy browser: everything you request goes through one of their servers (meaning, they know your every request and could read all of it) so those servers can do some compression and save you bandwidth. Sometimes only HTTP will get compressed, but here Nokia's browser will compress everything for you, including HTTPS. The issue isn't so much that they do it, but that this is a default browser and doesn't say this very obviously to users.
If you trust that proxy, then you'd be as secure as before, though I suppose every time you add a party to a communication line, you increase security risks.
The next question would be, how secure are their servers and how long before they are hacked and passwords, credit card numbers etc, are hijacked?
Exactly. I suppose any proxy browser has this extra security issue. Also of course how much you trust the proxy machine owners themselves.
As I'm sure we each understand, this practice is never secure. Most proxies have decent security but not total security. If their proxy services are breaking down HTTPS data then all of this data is insecure. I will not use opera to do anything secure, nor will I use skyfire. If I can shut the compression off for fast browsing I'll have to look into if the HTTPS data is kept intact.
This is troubling.
Some proxy browsers only do HTTP, while others do both HTTP and HTTPS. You could choose which one you want.
It's not all Operas, it's specifically Mini. Plus any other Operas where you've chosen to turn on Turbo.
Not that Opera matters anymore, seeings how they are gone gone gone. They are webkit now. The monoculture is now almost complete.
Combining compression with encryption: offtopic but interesting https://bugzilla.mozilla.org/show_bug.cgi?id=779413
This is referring to the HTTP "replacement" SPDY, developed by two dudes at teh googles. HTTP2 guys are now looking at something else for solving the compression problem because of these discovered these vulnerabilities.
Thanks... Then I'll be sure to turn off Turbo. Pisses me off though :eek: I wish they weren't gone, gone, gone as I liked them, but don't rely on them much any more
@Stomme_poes ; thanks for this interesting [ot] as it is interesting how one can exploit these vulnerabilities. Not so hard to exploit really!
No, it's neat how it's just a wee bit of python!
This topic is now closed. New replies are no longer allowed.