[regression] no connection with openconnect
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
openconnect (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Precise |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Since Oneiric it is no longer possible to connect to various servers
In Comment 4 in Bug 881720 a developer explains the details
(https:/
I'll paste them here again as this issue was not addressed in the other bug:
-------
dwmw2 (dwmw2) wrote on 2011-10-29: #4
pittipatti is correct. I'll elucidate...
Long ago (commit 3bee59c in v2.26) we switched from using TLSv1 to SSLv3, because some servers (or their firewalls) seem to reject any connections with Hello extensions.
In v3.11 (commit 4ad3d6c) we changed that again, because some servers also reject SSLv3 connections. Now we use TLSv1 but explicitly disable extensions. This should work everywhere.
We have *also* made openconnect export this code as a proper shared library, so when things like that are updated it will automatically take effect in the auth-dialog too. Older versions (including v3.02) only exported a *static* library because we weren't quite ready to call the API "stable" at that point.
What you need to do is update the openconnect package and make sure you're installing the shared library, and then make sure your network-
------
So please update to a version >= 3.11 to make this package usable again.
Thanks
Make it at least 3.13. There are important DTLS compatibility fixes in 3.12, and in 3.13 I made it build on Debian again... which is probably going to be helpful for you. 3.14 and 3.15 are just translations and Solaris/OSX/*BSD compatibility, so 3.13 would be OK... but why not just update to 3.15?