Opera 12.17 no longer works with https for me
-
rseiler last edited by
The setting for ALL sites is the one that I mentioned in opera:config. It's unchecked per your screenshot, so you're done. The override.ini is only for individual sites.
Just keep in mind what I mentioned on May 27th. The need to disable OCSP was only a temporary thing early on in this thread. Leaving it disabled creates debilitating performance issues on some sites.
-
Deleted User last edited by
I wonder what happened with the REAL Opera (before 12.17) developers community...
Are they all dead?
Are they all gagged by no disclosure agreements after they signed with evil G00gle?
Will their family be killed if they patch security holes and release Opera 12.18?
I mean... come on... nobody abandoned a very much loved project especially when a corporation stole open source projects just to kill the competition. It's obvious what G00gle did was a takeover because their $hitty Chrome is a joke.I didn't expect such betrayal from former Opera 12 programmers...
-
4oh4 last edited by
Signed with Google? AFAIK Opera just decided to stop developing their own HTML/layout engine and instead switch to one developed by multiple parties. For some reason they also decided to build an entirely new browser around that.
I guess the Opera spirit lives on in Vivaldi:
http://vivaldi.com/ -
rseiler last edited by
Since this thread was bumped anyway, all of the above problems were solved with 12.18.
-
4oh4 last edited by
Thanks. How did you find out about it? I'd never think to search for it.
You can get it here:
http://www.opera.com/download/guide/?os=windows&ver=12.18&local=y
http://www.opera.com/download/guide/?os=windows&list=all(Silly that there's no obvious way to get there using the site navigation. Luckily a search engine finds it.)
No changelog:
http://www.opera.com/docs/changelogs/windows/ -
4oh4 last edited by
Is there any reason to leave TLS 1.1 and 1.2 in their default, disabled, state? What about SSL3?
(No way to edit posts?)
-
4oh4 last edited by
Some details on the v12.18 update here:
http://www.opera.com/blogs/security/2016/02/opera-12-and-opera-mail-security-update/ -
bluejeans last edited by
Great news! Thanks, folks! There's still a little life left in The Real (Presto-based) Opera!
Now that I've updated to 12.18, what do you suggest I should do with the security settings?
TLS 1.1, TLS 1.2 - disable/enable? OCSP Validate Certificates?
-
-
blackbird71 last edited by adminI'd suggest disabling the OCSP validation, at least if it causes excessive CPU usage. See my May 2015 post above for some OCSP details: https://forums.opera.com/post/76110
Only if Opera's CRL lookup process is failing for some reaon or goes unsupported by Opera would one necessarily need to use the alternative OCSP option. Both CRL and OCSP are look-up processes to check if a security certificate on the system or browser has been revoked for some reason (cert hacking or counterfeiting being two such reasons).
-
bluejeans last edited by
So I've enabled TLS 1.1 and 1.2. Additionally, I've turned on SSL3 too (it was off). I've left OCSP validation off. Thanks for the helpful and quick replies!
-
rseiler last edited by
Though OCSP=0 is what caused the excessive CPU usage for me back then. I haven't disabled it again since then.
-
blackbird71 last edited by
Though OCSP=0 is what caused the excessive CPU usage for me back then. I haven't disabled it again since then.
Ahh... I apparently missed that somehow and got your experience backwards. In any case, one can always try it either way and see what happens, remembering to reverse the setting and try again if it creates an issue.
-
blackbird71 last edited by
So I've enabled TLS 1.1 and 1.2. Additionally, I've turned on SSL3 too (it was off). I've left OCSP validation off. Thanks for the helpful and quick replies!
I would be cautious about enabling SSL3 unless/until you encounter a site you must use that requires it - and then only for that site if the site security isn't that critically needed. SSL3 is now considered a weak or exploitable protocol, in particular regarding "Poodle" attacks that started a year or so ago. See:
https://wiki.openssl.org/index.php/SSL_and_TLS_Protocols#POODLE_:_SSLv3_harmful -
bluejeans last edited by
@blackbird71 Aha, nice of you to warn me. I remember incorrectly, and thought the exploit was for SSL2.
@rseiler As for OCSP, I suppose I'll turn it on and see if the CPU spikes less or more than what I'm used to.
Great forum!
-
A Former User last edited by
"Since this thread was bumped anyway, all of the above problems were solved with 12.18."
The https blockade problem? No, it is still there (or again?).
-
-
A Former User last edited by
Example?
Maybe I made an error: now, when I test it, 12.18 does not block the https sites which I tested.
-
A Former User last edited by
If it happens again, heed which sites were open in other tabs, then the site(s) (and page) where the problem occurs, plus your current browser settings - if you change some. It might be a temporary setting - like Turbo on/off, or
show/don't showimages... Besides, your current connection specs may be changing...
Which type of internet connection are you on generally?
