Opera 12.18

[plovec]

plovec last edited by

It's not working in 12.17 today, either. It's probably a coincidence. dragonfly.opera.com is down.

Have you tried to uncheck this option

opera:config#DeveloperTools|ProxyAutoConnect

it should avoid the autoupdate of opera dragonfly

If you don't have dragonfly offline maybe this could help:
https://opvardarchive.wordpress.com/2008/05/07/opera-dragonfly-is-here-and-it-works-offline/

[empej107]

empej107 last edited by

No linux and MacOS builds.
"Further, as we don’t see a significant number of users of Opera 12 and Opera Mail on non-Windows platforms, we won’t be updating for those."
WTF? It's really so expensive or labour-intensive?

What a pity.

I thought that the Linux users were (are) a significant amount of total users of Opera 12.*.

Beside that, it looks like there were some modifications into binaries. Replacing only op*.dat files did not help for the previous version of the browser so we are dependent on the mercy of Opera.

The solutions seem to be using Wine or a proxy exclusively for those problematic sites.

[torrente]

torrente last edited by

Awesome news, thank you Opera. Works fine, no more https errors.

[A Former User]

A Former User last edited by

Ohhh, the Opera Presto update screen, I never thought I'd see you again!!
:love: :love: :love:

[A Former User]

A Former User last edited by

I got the update message and said no because thought it wanted to update to new opera. I hope it will fix the frequent closing issue.

[rseiler]

rseiler last edited by

When were you seeing frequent closing issues with 12.17? I can recall one that related to certain security protocols, but not a lot of people saw it, and I think it's gone now.

[A Former User]

A Former User last edited by

When were you seeing frequent closing issues with 12.17? I can recall one that related to certain security protocols, but not a lot of people saw it, and I think it's gone now.

It closed on me all the time and could not pin it down to any site or anything. That and taking way too long to load some sites like news sites were my two main issues. And some site did not work anymore(chase bank for one) but most that didn't work work security related, fatal error 40, 80, etc

[Deleted User]

Deleted User last edited by

omg, unbelievable!
https working again for most sites.

thanks to the devs that have not forgotten the old users.

[A Former User]

A Former User last edited by

Yes, I've been plagued with sudden shutdowns on Opera 12.17 for months.
I thought it was related to a plugin (specifically Flash) but have never been able to completely confirm that.
So far so good, not had any yet, and I'm hoping that it won't happen with 12.18.

[rseiler]

rseiler last edited by

Had you ever enabled TLS 1.1 and 1.2 in 12.17? That would cause random crashes for me. It's not a problem in 12.18, however.

[A Former User]

A Former User last edited by

I would appreciate some advice on what the recommended security protocol settings are now for 12.18.
On 12.17, I had SSL 3 deselected, and TLS 1, 1.1, and 1.2 all selected, and that's how they still are now on 12.18.
IIRC I did have one of the TLS options deselected for quite a long time, but then I found a website that wouldn't work without it.
So, what's the recommended best settings now for compatibility and security?
Any advice welcome.

[rseiler]

rseiler last edited by

The one important thing is SSL3 off. After that, as you say, you will still occasionally find a site that needs TLS1, so that's probably why they left it enabled. As I recall, negotiation goes from the top down, so it's not as if having all the TLS's enabled means that TLS1 would be used over TLS 1.2 if the site supported 1.2.

Even Chrome, which might be the most aggressive of the browsers in this arena, has TLS1 enabled (Firefox does too).

[blackbird71]

blackbird71 last edited by

The negotiation normally starts by seeking the highest-grade protocol that can be employed by the browser and site together and which supports a mutually-available encryption cipher associated or available for the protocol, all as specified in the site-cert. If one can't be agreed upon, the negotiation moves downward until it (hopefully) finds one that works. In a sense, the site server is the partner who should best understand the security requirements of the possible transactions it supports and should be the one to call off the negotiation if a suitably safe protocol and encryption cipher can't be agreed upon - whereupon the browser reports it's unable to talk securely to the site.

However, some sites' protocols and encryption requirements/certs aren't well thought through and will negotiate down to protocols whose traffic/encryption can perhaps be too readily cracked or hijacked... in which case, a knowledgeable user may elect to block (uncheck) lesser protocols within his own browser, just in case. In too many cases, 'lazy' sites will only offer a lowest-grade protocol, take it or leave it, so that a user has to accept low-grade protocols or forego the site entirely. And a complicating factor in all this is that all the TLS protocols have certain weaknesses (though fewer than the SSLs), some arguably easier to possibly exploit than others, so that one can't necessarily just argue that TLS1.2 is "safer" than TLS1.1 under all conditions.

At the end of the day, a knowledgeable user has to use whatever he finds works best for him and those secure sites he uses. Less knowledgeable users probably should just turn on whatever is available if browser compatibility with all sites is desired over technically-best traffic security.

[bkazmierczak]

bkazmierczak last edited by

I'm glad we were able to make some of you guys happy. Thanks for good words!

[A Former User]

A Former User last edited by

I'm glad we were able to make some of you guys happy. Thanks for good words!

Much appreciated. Working pretty good now

[A Former User]

A Former User last edited by

Yes, it is very much appreciated.
Presto Opera is still the best browser ever made in the eyes of many people, especially those who appreciated its almost total personal user customisation facilities.
The reasons for dropping it are well documented and completely understandable, but it was still a very sad day when it was seemingly abandoned for what many saw as an inferior substitute.
Thank you so much for keeping the security and compatibility issues of its die-hard users still in mind, I can't imaging the developers of say Google Chrome ever doing that!
:cheers:
With regard to the security settings, thanks for all the advice guys, it sounds as if it will be fine left as it is.
And I still haven't had any more unexplained sudden shutdowns (touches wood)!

[A Former User]

A Former User last edited by

Sorry, back again!
As this relates only to Opera 12.18 I didn't want to start another thread, but can anyone remember how you get rid of that extremely annoying (and now completely unnecessary IIRC) popup that says "click to activate and use this control" on plugins on later versions of Presto Opera?

I have the xa-nocta batch file and associated scripts which I always used to use to get rid of the bloody thing, but that no longer works on more recent versions. There was a hex edit solution as well IIRC, if we're allowed to mention such things!
I think there was an extension too, but I don't really want to use that as IIRC it only worked for YouTube videos.

The annoying thing is that I'm sure I did it for 12.17, but I now can't remember how as it's so long ago!
It doesn't seem to be a problem with the 64bit version of 12.18 BTW (I use both 32bit and 64bit versions on different operating systems).
Anyone any ideas to jog my memory?

[sgunhouse]

sgunhouse Moderator Volunteer last edited by

There was a setting presuming you aren't using Turbo…

I'm on my tablet now and can't look, but it should be in opera:config somewhere.

[A Former User]

A Former User last edited by

This isn't anything to do with the plug-ins only on demand setting.
It's to do with the wretched Eolas patent nonsense, which has now been struck down.
For some reason Opera never seem to have removed the code to prevent plug-ins running automatically, even though the patent hasn't applied since 2012.

[rseiler]

rseiler last edited by

I was thinking about that Eolas thing yesterday, but I have yet to see it happen in 12.18 x86 (testing Flash), and I couldn't recall doing it for 12.17, so I thought that somewhere along the line that Opera itself finally added the "capability." After all, that lawsuit, or whatever it was, was concluded years ago.

Can you give me an example page?

It was always a patch (at least that I recall), never an opera:config setting (that's way too easy).

All that said, I do see now that my 12.17 Opera.dll had two bytes in it changed from the original, but I have no documentation of why that is all this time later. I thought the Eolas patch (I used xa-nocta too, at least for a while) changed more than two bytes.