I wouldn't like to disable TLS 1.1/1.2 and left TLS 1.0 enabled, because 1.0 vulnerable to BEAST attack. > ...
And that, in a nutshell, is but one of the obsolescence dilemmas in which Presto Opera users increasingly find themselves. Namely, if they mitigate the SSL3 protocol vulnerability by enabling just TLS 1.2, 1.1, and 1, they risk stumbling over expired certs at any of those levels, depending on which ones the site downward-security-protocol-negotiation might encounter first; if they minimize the exposure to expired certs by enabling only TLS 1, they risk the documented TLS 1 protocol vulnerability in that way. The digital online world continues to change; Presto Opera is essentially frozen in time and will remain so... and there's only so much that can be done to work around the growing number of missing pieces.
Opera may or may not find it in its own best interests to update Presto Opera's certs... they certainly have little reason to do that if their focus is on expanding adoption of their Blink Opera version(s). At some point, common sense dictates Opera ASA will say "no more" in terms of bailing out Presto users. This is a key point that ought to drive users to move away from Presto Opera to a new flavor of browser (be it Blink Opera or somewhere else) if such obsolescence issues matter to them, and sooner rather than later. If users can live with these kinds of issues, then of course their life with Presto can go on.
