Description of problem: When configuring OpenVPN using the NetworkManager UI, there is no option to specify CRL against which to check the server certificate provided by the OpenVPN server. Version-Release number of selected component (if applicable): NetworkManager-openvpn-1.8.0-3.fc27.x86_64 NetworkManager-openvpn-gnome-1.8.0-3.fc27.x86_64 openvpn-2.4.5-1.fc27.x86_64 How reproducible: Create a new OpenVPN connection using the NetworkManager UI. Steps to Reproduce: 1. Start creating a new OpenVPN connection using the NetworkManager Actual results: There is no place where the user can specify CRL which can be used to validate server certificate Expected results: In the UI the user should be able to provide CRL that should be used to validate the server certificate. Additional info: This increases the risk of MITM attacks because if the server key is compromised and revoked, the client will still connect to that server if the cert is not validated using CRL.
are you talking about the --crl-verify option? Only that? In general, in Fedora we only package what is implemented upstream at https://git.gnome.org/browse/network-manager-openvpn/. Hence, a feature request is better done in the upstream bug tracker https://bugzilla.gnome.org/enter_bug.cgi?product=NetworkManager I would like to send you there, but I cannot promise you that anybody fixes this any time soon. Bugs/Features get fixed/implemented whenever somebody decides to work on them... but maybe somebody is gonna do it, who knows?
Hey, thanks for the quick response. I did that mistake the last time also. I found this https://bugzilla.gnome.org/show_bug.cgi?id=782309 one and I'm going to relate it here.
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '27'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 27 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.