Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
NetworkManager-vpnc has no option to use the "Hybrid" auth mechanism available in vpnc. This causes the server to be validated by a certificate, then the client authenticates via xauth. This is to prevent exposure of the group password from enabling MitM attacks against users trying to connect to the VPN.
Version-Release number of selected component (if applicable):
NetworkManager-0.8.1-5
Expected results:
- Ability to set hybrid mechanism and certificate via NetworkManager-vpnc
Comment 2RHEL Program Management
2011-04-04 02:01:21 UTC
Since RHEL 6.1 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.
Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.
Since this affects anyone who is using two-factor auth with WPA (and hopefully in a corporate environment, there should be some of these). The patch to do this is already in the code, just disabled.
Everything we care about is now upstream, both in vpnc and in NetworkManager-vpnc, so could be backported to EPEL. Since neither vpnc or NetworkManager-vpnc are actually RHEL components, it's up to people who work on EPEL to do the builds for EPEL, unless you can convince PM that RHEL should officially support vpnc and NetworkManager-vpnc.
But in any case, all the pieces are there, and the Fedora updates have just been submitted for F15 and rawhide so the EPEL stuff would just be backporting.