New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade OpenSSL version from 1.0.0g #6
Comments
Like someone on /g/ just mentioned it might be worth using LibreSSL instead, although the codebase for that is a lot different to OpenSSL IIRC so merging the Opera changes into it might be a bit of a hassle. Also not sure if they have API compatible 1.0.x releases or not, if not it'd probably take some work to get Opera to work with it (probably wouldn't be much more difficult than the API changes needed for OpenSSL 1.0.2 though) |
There is a guy who made a patch which updates the OpenSSL to 1.0.0q. Would that solve the problem? Just asking. |
Any news regarding this issue? |
Hey, some guy created OpenSSL 1.0.0q, 1.0.0t, 1.0.1u and 1.0.2l patches for Opera: |
Those patches are out-of-date and don't integrate fully with the browser (most secure sites still don't work even after applying one of them). |
Well, if it fixes the error 40-es on most sites, then it's better than nothing. |
I don't think they do. |
The readme says otherwise. Needs testing. |
I think they did do what is stated in the readme. |
The OpenSSL in here is pretty ancient, and doesn't support the GCM cipher used in 12.18.
Unfortunately we can't just do an in-place upgrade since they've customized the code for it a little, but with some work it could probably be upgraded to 1.0.2j.
Not sure if just upgrading OpenSSL will get GCM working though, probably need to add some glue code in the actual Opera src somewhere for it to use it.
The text was updated successfully, but these errors were encountered: