Launchpad has imported 8 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=1228426.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2015-06-04T22:29:50+00:00 Jonas wrote: Description of problem: When activating OpenVPN without DHCP6, random traffic will be routed without VPN if the basic physical network device has IPv6 connectivity. This is a security issue, since a user activating the VPN would expect all go through it. When I activate a VPN that doesn't support V6, obviously V6 routes need to be removed entirely to ensure everything goes through the VPN as the user would expect. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: Reply at: https://bugs.launchpad.net/ubuntu/+source/openvpn/+bug/1476769/comments/0 ------------------------------------------------------------------------ On 2015-06-04T22:39:16+00:00 Jonas wrote: Thanks to #1228427 it appears I can't easily use OpenVPN through the networkmanager gui in this wifi network *at all*. That sucks, it would be really awesome if you could do something to fix that.. Reply at: https://bugs.launchpad.net/ubuntu/+source/openvpn/+bug/1476769/comments/1 ------------------------------------------------------------------------ On 2015-06-05T06:51:11+00:00 Pavel wrote: This is indeed an interesting problem also described in bug #1091356 that is not specific to NetworkManager. A machine with IPv4 and IPv6 connectivity and IPv4 VPN connectivity with IPv4 and IPv6 DNS information from the VPN will always attempt to reach hosts via IPv6. > This is a security issue, since a user activating the VPN would expect all go through it. There are two issues, actually: 1) Serving IPv6 DNS records and providing VPN access without IPv6 at the same time is a security problem in the first place. Clients that only use VPN for resources on the network are thus not informed about the IPv6 subnets that constitute resources on the network. Solutions (on the network operator side): a) Avoid IPv4-only VPNs and only provide IPv4+IPv6 VPNs. b) Don't provide IPv6 DNS records on IPv4-only VPNs (and vice versa). 2) When VPN is to be used for all (except local) resources and only IPv4 connectivity is available on the VPN, there should IMO be no IPv6 default route through the local router just as there is no IPv4 default route through the local router. >From the network configuration point of view the second issue is as follows... Expected result: * IPv4 default route through VPN * IPv6 default route absent (as VPN doesn't provide any) Actual result (as I understand the bug report): * IPv4 default route through VPN (good) * IPv6 default route via local gateway (bad) Reply at: https://bugs.launchpad.net/ubuntu/+source/openvpn/+bug/1476769/comments/2 ------------------------------------------------------------------------ On 2015-08-18T14:59:01+00:00 Fedora wrote: This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. Reply at: https://bugs.launchpad.net/ubuntu/+source/openvpn/+bug/1476769/comments/6 ------------------------------------------------------------------------ On 2015-11-04T10:46:32+00:00 Fedora wrote: This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. 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 '21'. 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 21 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. Reply at: https://bugs.launchpad.net/ubuntu/+source/openvpn/+bug/1476769/comments/7 ------------------------------------------------------------------------ On 2015-11-04T17:50:19+00:00 Jonas wrote: Still present in Fedora 22 Reply at: https://bugs.launchpad.net/ubuntu/+source/openvpn/+bug/1476769/comments/8 ------------------------------------------------------------------------ On 2016-07-19T19:10:29+00:00 Fedora wrote: Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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. Reply at: https://bugs.launchpad.net/ubuntu/+source/openvpn/+bug/1476769/comments/9 ------------------------------------------------------------------------ On 2016-07-26T04:35:21+00:00 Jan wrote: This bug appears to have been reported against 'rawhide' during the Fedora 25 development cycle. Changing version to '25'. Reply at: https://bugs.launchpad.net/ubuntu/+source/openvpn/+bug/1476769/comments/10 ** Changed in: fedora Status: Unknown => Confirmed ** Changed in: fedora Importance: Unknown => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1476769 Title: When activating OpenVPN without DHCP6, random traffic will be routed without VPN Status in network-manager package in Ubuntu: Confirmed Status in openvpn package in Ubuntu: Confirmed Status in Fedora: Confirmed Bug description: When activating an OpenVPN without DHCP6 through NetworkManager, random traffic will be routed without VPN if the basic physical network device has IPv6 connectivity but the VPN hasn't. This is a security issue, since a user activating the VPN would expect all go through it. network-manager package version: 0.9.10.0-4ubuntu15.1 Steps to reproduce: 1. Find some VPN without IPv6 routing or DHCP6. Get the according openvpn configuration file and import into NetworkManager 2. Make sure your physical networking device has native IPv6 access 3. Activate the VPN in the network settings Expected result: * IPv4 default route through VPN * IPv6 default route absent (as VPN doesn't provide any) Actual result (as I understand the bug report): * IPv4 default route through VPN (good) * IPv6 default route via local gateway (bad) ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: openvpn 2.3.2-9ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8 Uname: Linux 3.19.0-21-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Jul 21 19:21:50 2015 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=<set> LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: openvpn UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1476769/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
