Bug 1425859
| Summary: | Can't connect to VPN after upgrade | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Bastien Nocera <bnocera> |
| Component: | openvpn | Assignee: | David Sommerseth <dazo> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 26 | CC: | choeger, dazo, dcbw, gwync, huzaifas, jfrieben, lkundrak, mauricio.teixeira, psimerda, steve, thaller |
| Target Milestone: | --- | Keywords: | Regression |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | openvpn-2.4.1-1.fc26 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-04-01 17:28:45 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Bastien Nocera
2017-02-22 15:42:17 UTC
NetworkManager-openvpn plugin just calls openvpn. So, if the plugin does something wrong, it means it calls openvpn with wrong arguments. But from the given information, I don't see that being the case. Reassigning to openvpn.
OpenVPN v2.4 on Fedora is currently using mbedtls-2.{3,4} instead of OpenSSL, due to building issues against OpenSSL v1.1.
The mbedtls-2.x versions *by default does not accept* any RSA certificates signed by a CA with a key less than 2048 bits.
IIRC, this behaviour may be changed in mbed TLS, but it is a build-time option. So the whole mbed TLS library needs to be reconfigured.
With all this said, there are now patches on the openvpn-devel mailing list under review which enables OpenVPN to be built against OpenSSL v1.1 as well as v1.0.
Currently the only workaround I can see is to recompile the mbed TLS library to allow weaker CA keys.
This bug appears to have been reported against 'rawhide' during the Fedora 26 development cycle. Changing version to '26'. (In reply to David Sommerseth from comment #2) > OpenVPN v2.4 on Fedora is currently using mbedtls-2.{3,4} instead of > OpenSSL, due to building issues against OpenSSL v1.1. > > The mbedtls-2.x versions *by default does not accept* any RSA certificates > signed by a CA with a key less than 2048 bits. > > IIRC, this behaviour may be changed in mbed TLS, but it is a build-time > option. So the whole mbed TLS library needs to be reconfigured. > > With all this said, there are now patches on the openvpn-devel mailing list > under review which enables OpenVPN to be built against OpenSSL v1.1 as well > as v1.0. > > Currently the only workaround I can see is to recompile the mbed TLS library > to allow weaker CA keys. Could we have that in rawhide soon? I haven't been able to use that VPN for a week. This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. After downgrading a Fedora 26 system to openvpn-2.4.0-1.fc25. OpenVPN seems to work: it is possible to connect successfully to an OpenVPN server which did not work with openvpn-2.4.0-2.fc26. Please try the latest openvpn-2.4.1-1.fc26. This have an additional Fedora specific patch which permits mbed TLS to accept weaker RSA keys and hashing algorithms (so called 'legacy certificate profile') https://bodhi.fedoraproject.org/updates/openvpn-2.4.1-1.fc26 openvpn-2.4.1-1.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-f41671c546 openvpn-2.4.1-1.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report. |