** Changed in: network-manager (Ubuntu Xenial)
Status: Confirmed => Won't Fix
** Changed in: systemd (Ubuntu Xenial)
Status: Invalid => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu
** Changed in: network-manager
Status: Confirmed => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1754671
Title:
Full-tunnel VPN DNS leakage regression
St
bugzilla.gnome.org is being shut down in favor of a GitLab instance.
We are closing all old bug reports and feature requests in GNOME Bugzilla which
have not seen updates for a long time.
If you still use NetworkManager and if you still see this bug / want
this feature in a recent and supported
1.10.6-2ubuntu1.2 has cause a regression in functionality.
Anyone using a "split" VPN, where there is no default route, AND wish to
have DNS services supplied by the server to be honoured, via use of the
ipv4.dns-priority parameter, will have this broken. This is a bit of a
sore point considering
The verification of the Stable Release Update for network-manager has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you enc
This bug was fixed in the package network-manager - 1.10.6-2ubuntu1.2
---
network-manager (1.10.6-2ubuntu1.2) bionic; urgency=medium
[ Till Kamppeter ]
* debian/tests/nm: Add gi.require_version() calls for NetworkManager
and NMClient to avoid stderr output which fails the test
I have just run the test case from this bug description on the bionic-proposed
version 1.10.6-2ubuntu1.2.
tcpdump does not show any leak of the VPN-specific queries. I have not observed
other issues in my tests.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verif
No worries about my previous comment, it is solved.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1754671
Title:
Full-tunnel VPN DNS leakage regression
Status in Network
Now network-manager is hanging on (all autopkg tests passed):
Not touching package due to block request by freeze (contact #ubuntu-
release if update is needed)
Which freeze do we currently have on Bionic?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded pac
The netplan.io (arm64) autopkgtest failure (due to timeout) has been retried
today, it passed:
http://autopkgtest.ubuntu.com/packages/n/netplan.io/bionic/arm64
No more failure reported in pending sru page.
- Eric
--
You received this bug notification because you are a member of Ubuntu
Touch se
All autopkgtests for the newly accepted network-manager (1.10.6-2ubuntu1.2) for
bionic have finished running.
The following regressions have been reported in tests triggered by the package:
network-manager/1.10.6-2ubuntu1.2 (amd64, arm64, i386, ppc64el)
systemd/237-3ubuntu10.31 (i386, ppc64el)
ne
Hello dwmw2, or anyone else affected,
Accepted network-manager into bionic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/network-
manager/1.10.6-2ubuntu1.2 in a few hours, and then in the -proposed
repository.
Please help us by testing this new pack
Sorry for the late reply, I was on a conference last week.
I installed the PPA now and tested with the reproducer of the initial
posting. This works for me. Also the machine in general seems to work OK
with this version of network-manager.
Thank you very much Dariusz for packaging this version.
This fix was first included in upstream 1.12.0, so this was actually
fixed in Cosmic with network-manager 1.12.2-0ubuntu3
** Changed in: network-manager (Ubuntu Cosmic)
Importance: Undecided => High
** Changed in: network-manager (Ubuntu Cosmic)
Status: Won't Fix => Fix Released
--
Yo
Great work, thank you very much!
It will need some testing of which I can only test the reproducer in the
initial description of this bug report, not any regressions which the
first attempt of upstream-update-based SRU, as I could not reproduce
these by myself.
So I would say to take this as a ne
I have backported what was listed as nm-1-10 fix for the bug in the upstream
bugzilla [1].
I have also applied fixes for bug #1825946 and bug #1790098 to it.
[1]
https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=1e486a721de1fec76c81bfc461671a7fbdae531b
After testing this buil
** Bug watch removed: bugzilla.gnome.org/ #766769
https://bugzilla.gnome.org/show_bug.cgi?id=766769
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1754671
Title:
Full-t
Launchpad has imported 73 comments from the remote bug at
https://bugzilla.gnome.org/show_bug.cgi?id=746422.
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
** CVE removed: https://cve.mitre.org/cgi-
bin/cvename.cgi?name=2018-15688
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1754671
Title:
Full-tunnel VPN DNS leakage regres
I have worked out the problem with the new NetworkManager which required
me to set ipv4.dns-priority=-1 (which, in turn, messes things up for
those with fresh installs that don't get the new NetworkManager).
The new NM sets ipv4.dns-search=~. automatically for full-tunnel VPNs
but it doesn't also
Any word on when this CVE will be fixed?
In the meantime I have put the 1.10.14-0ubuntu2 package into an apt
repository at http://david.woodhou.se/cve-2018-1000135/ for users who
need it. I couldn't work out how to copy it into a PPA without
rebuilding it.
In the short term can someone please at
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: network-manager (Ubuntu Xenial)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://b
> That's weird, do you understand why? The update was deleted so you should be
> back to initial
> situation, we had no change to the previous package build
Other package changes? Certainly systemd-resolver although we don't use
that (because of a previous VPN DNS leak problem) we use dnsmasq.
seb128, it seems that dwmw2 NEEDS this SRU, without he does not get his
environment working correctly, with SRU he gets it at least working
setting the parameters he mentioned. I asked the posters of the
regressions whether they get their situation fixed when using this SRU,
the systemd SRU and dwm
> Then the NM update was pulled, and new installations aren't working at
all, even if we don't set the DNS config as described.
That's weird, do you understand why? The update was deleted so you
should be back to initial situation, we had no change to the previous
package build
Also Till is still
Do we have any idea when this will be fixed? Most of my users used to
get away with the DNS leakage and it was "only" a security problem but
stuff actually worked. Then the NM and other updates were shipped, we
set ipv4.dns-priority=-1 and ipv4.dns-search=~. and it all worked fine.
Then the NM upda
This was fixed in systemd 237-3ubuntu10.22 for bionic, and
239-7ubuntu10.14 for cosmic. I missed a "#" in the changelog (sorry) so
the tooling didn't automatically mark this bug as fix released.
** Changed in: systemd (Ubuntu Bionic)
Status: Fix Committed => Fix Released
** Changed in: sy
I have checked again on Bionic, making sure that the installed systemd
actually comes from the bionic-proposed repository, that the behavior
according to the test case shown in the initial description of this bug
is correct, DNS queries of destinations in the VPN done through the
VPN's DNS and DNS
@ddstreet We don't use systemd-resolver here. It's fairly trivial to set
up a VPN service; the openconnect 'make check' uses ocserv
automatically, for example. You shouldn't have difficulty reproducing
this locally.
--
You received this bug notification because you are a member of Ubuntu
Touch se
We are not going to do cosmic/n-m changes at this point, best to upgrade
to Disco if you need that issue resolved
** Changed in: network-manager (Ubuntu Bionic)
Assignee: Olivier Tilloy (osomon) => Till Kamppeter (till-kamppeter)
** Changed in: network-manager (Ubuntu Cosmic)
Status:
@dwmw2 and/or @till-kamppeter, can you verify the systemd upload for
this bug for b and c?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1754671
Title:
Full-tunnel VPN DN
bug #1831261 is also described as a potential side effect from this
change
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1754671
Title:
Full-tunnel VPN DNS leakage regres
> Is this going to be fixed in disco?
speaking for systemd only, the commit needed is
a97a3b256cd6c56ab1d817440d3b8acb3272ee17:
https://github.com/systemd/systemd/commit/a97a3b256
that's included starting at v240, so is already in disco.
--
You received this bug notification because you are a
Is this going to be fixed in disco?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1754671
Title:
Full-tunnel VPN DNS leakage regression
Status in NetworkManager:
Fix R
systemd accepted to bionic/cosmic-proposed, please test
** Tags removed: verification-failed verification-failed-bionic
** Tags added: verification-needed verification-needed-bionic
verification-needed-cosmic
** Changed in: systemd (Ubuntu Cosmic)
Status: In Progress => Fix Committed
**
Uploaded patched systemd to b/c queues.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1754671
Title:
Full-tunnel VPN DNS leakage regression
Status in NetworkManager:
F
** Tags added: ddstreet-next
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1754671
Title:
Full-tunnel VPN DNS leakage regression
Status in NetworkManager:
Fix Released
** Also affects: network-manager (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu Cosmic)
Assignee: (unassigned) => Dan Streetman (ddstreet)
** Changed in: systemd
And (in case any of my colleagues are paying attention and inclined to
do it before the next time I get to spend any real time in front of a
computer, next week), without the dns-priority and dns-search settings
that made it work again after the recent NM update.
--
You received this bug notifica
dwmw2, yes, exactly for this case.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1754671
Title:
Full-tunnel VPN DNS leakage regression
Status in NetworkManager:
Fix Re
Till, you want that for the case where dnsmasq is being used and is
misbehaving?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1754671
Title:
Full-tunnel VPN DNS leakage
Please create the following files (and directories if needed for them):
1. /etc/systemd/journald.d/noratelimit.conf containing
RateLimitIntervalSec=0
RateLimitBurst=0
2. /etc/NetworkManager/conf.d/debug.conf
[logging]
level=TRACE
domains=ALL
Then restart journald:
sudo systemctl restart syste
On the 1.10.14 regression simply making those dns-priority/dns-
search settings the *default* behaviour for a full-tunnel VPN would
appear to be the correct thing to do (i.e. use the DNS of a full-tunnel
VPN for *all* lookups), and I think it should resolve the problems
people were seeing.
--
On the switch to using dnsmasq: that decision predates my tenure so I
have limited visibility. I can try to get our IT team to expend effort
in moving to systemd-resolved and see what breaks. It may even be
completely unnecessary in xenial, and is merely inherited to make our
bionic setups less dif
Dammit, "completely unnecessary in bionic but inherited from xenial"...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1754671
Title:
Full-tunnel VPN DNS leakage regressio
Due to the SRU regressions reported in LP: #1829838 and LP: #1829566, I
have reverted this SRU for the moment, restoring network-manager
1.10.6-2ubuntu1.1 to bionic-updates. I am marking this bug
verification-failed pending resolution of the reported regressions.
** Changed in: network-manager (U
> These systems are using dnsmasq not systemd-resolver.
> This was done for historical reasons; I'm not sure of
> the specific bug which caused that choice.
NetworkManager in Ubuntu 16.04 and earlier defaulted to integrating with
dnsmasq. But on 18.04 and later, this integration has been delibera
This is Bionic.
After last week's update to 1.10.14-0ubuntu2 all my VPN users (who are
using dnsmasq) reported that DNS supported working for them while they
were on the VPN. Some internal names were looked up correctly, others
weren't.
I resolved it for them as follows:
$ sudo nmcli con modify
dwmw2, the systemd fix was mainly meant for people with standard
configuration where this fix is actually needed and solve the problem.
You are writing that adding "dns-priority=-1;dns-search=~." solves the
problem for you. Where/to which file did you add this? Do you need this
already with the or
We aren't using systemd-resolver for various historical reasons; we are
using dnsmasq which should be expected to work. It isn't, but we have
manually added the dns-priority=-1;dns-search=~. settings which make it
work, as an emergency deployment when the latest NM update broke things
for everyone.
Unfortunately, the SRU for systemd did not yet get processed. Therefore
I have now uploaded this version of systemd to my PPA so that you can
already test/get your problem solved. Please tell here whether it
actually fixes the bug.
Here is my PPA:
https://launchpad.net/~till-kamppeter/+archive/ub
These systems are using dnsmasq not systemd-resolver. This was done for
historical reasons; I'm not sure of the specific bug which caused that
choice.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://
dwmw2, did you apply the systemd fix from comment #27? For this bug to
be fixed you need BOTRH the fixed packages of network-manager and
systemd.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.
I am receiving reports that it isn't fixed in 18.04 either. Users are
still seeing DNS lookups on the local network, until they manually edit
the VPN config to include:
[ipv4]
dns-priority=-1
dns-search=~.;
I thought that wasn't going to be necessary?
--
You received this bug notification becau
The original bug report was about a regression in 16.04 with the dnsmasq
integration. While I'm glad this got the ball rolling on the bionic
networkd integration, let's not forget that we broke xenial? Added a
xenial task for network-manager accordingly.
** Also affects: network-manager (Ubuntu
This bug was fixed in the package network-manager - 1.10.14-0ubuntu2
---
network-manager (1.10.14-0ubuntu2) bionic; urgency=medium
[ Till Kamppeter ]
* debian/tests/nm: Add gi.require_version() calls for NetworkManager
and NMClient to avoid stderr output which fails the test.
Will be releasing network-manager without the systemd part for now as it
poses no threat to the user.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1754671
Title:
Full-tu
Hello dwmw2, or anyone else affected,
Accepted network-manager into bionic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/network-
manager/1.10.14-0ubuntu2 in a few hours, and then in the -proposed
repository.
Please help us by testing this new packa
Good news, the network-manager SRU is not broken or wrong, but an
additional SRU, on systemd, is needed to actually fix this bug.
I got a hint from Iain Lane (Laney, thank you very much) to the
following fix in systemd upstream:
https://github.com/systemd/systemd/commit/a97a3b256
and backported
I have now done the test under [Test Case] in the initial description of
this bug report.
I have a completely updated (including -proposed) Bionic machine (real
iron, a Lenovo X1 Carbon 2nd gen from 2015) with network-manager
1.10.14-0ubuntu1
I have configured the Canonical VPN, both UK and US. I
** Description changed:
- * Impact
+ [Impact]
+ When using a VPN the DNS requests might still be sent to a DNS server outside
the VPN when they should not
- When using a VPN the DNS requests might still be sent to a DNS server
- outside the VPN when they should not
+ [Test case]
+ 1) Set up a
Based on comment #12 I am not sure that this is considered
"verification-done" by the relevant developers and there was no comment
given when the tags were changed. Resetting.
I also think there should be an affirmative test as part of this SRU
that the use case I described in comment #13 has not
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1754671
Title:
Looking at the upstream bug, it looks like the fix relies on reworking
large parts of the code and wouldn't be easy to SRU to Xenial.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.laun
@seb128 please see "In 16.04 the NetworkManager package used to carry
this patch..." in the bug description above.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1754
@dwmw2, 'This was a regression there caused by an earlier update.' would
give some details ont that? you should probably open another report
specifically about that if there was a regression in a xenial update
--
You received this bug notification because you are a member of Ubuntu
Touch seeded p
Is there a 16.04 package? This was a regression there caused by an
earlier update.
I have users reporting the same bizarre behaviour I wasn't able to
clearly describe before — essentially, DNS being sent out seemingly
random interfaces (sometimes VPN, sometimes local). My advice to just
install th
I can also confirm that the network-manager package version
1.10.14-0ubuntu1 from bionic-proposed fixes the issue.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1754
@dwmw2, as far as i understand, you should configuring DNS through
systemd-resolve only. Try remove your edits from `/etc/NetworkManager
/system-connections`, or even delete your connections from
NetworkManager interface, and create new. After that, establish vpn
connection and see at `systemd-reso
Not sure what happened there. It was looking up *some* names in the
$COMPANY.com domain on the VPN, but others not, consistently. I couldn't
see a pattern.
I have manually set ipv4.dns-search="~." and ipv4.dns-priority=-1 and
now it does seem to be behaving. However, this shouldn't be necessary.
T
Hm, that didn't last long. Now it isn't looking up *anything* in the VPN
domains. It's all going to the local VPN server. I don't know what
changed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
ht
network-manager-1.10.14-0ubuntu1 does seem to fix the DNS problem here;
thanks.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1754671
Title:
Full-tunnel VPN DNS l
@Steve (sorry for the late reply): not sure how that relates to bug
#1726124, but in my limited understanding of the changes, they shouldn't
regress the split-DNS use case.
Some relevant pointers to better understand the fixes and their context:
- https://bugzilla.gnome.org/show_bug.cgi?id=74642
I installed package of network-manager 1.10.14-0ubuntu1 from bionic-
proposed, and can confirm that version fixed dns leak: now when vpn
connection established it gets `DNS Domain: ~.` in systemd-resolve
automatically, so no more needed to manually apply command `systemd-
resolve -i tun0 --set-doma
How does this proposed change relate to LP: #1726124? Are users who are
currently relying on correct split DNS handling by network-manager
+systemd-resolved in bionic going to see this regress and have all DNS
requests now sent over the VPN when they aren't supposed to?
--
You received this bug
Please test and share your feedback on this new version here, but
refrain from changing the verification-needed-bionic tag for now. This
new version includes many changes and we want to give it an extended
testing period to ensure no regressions sneak in, before it is published
to bionic-updates. T
Hello dwmw2, or anyone else affected,
Accepted network-manager into bionic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/network-
manager/1.10.14-0ubuntu1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new packa
** Merge proposal unlinked:
https://code.launchpad.net/~osomon/network-manager/+git/network-manager/+merge/361051
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1
I've updated the description for the SRU but if someone had a better
description of a testcase that would be welcome
** Description changed:
+ * Impact
+
+ When using a VPN the DNS requests might still be sent to a DNS server
+ outside the VPN when they should not
+
+ * Test case
+
+ Configure
** Merge proposal linked:
https://code.launchpad.net/~osomon/network-manager/+git/network-manager/+merge/361051
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/175
The fix was backported to the upstream 1.10 series.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1754671
Title:
Full-tunnel VPN DNS leakage regression
Status in
This is fixed in the 1.12 series of network-manager (1.12.0 release), so
cosmic and dingo are not affected.
** Changed in: network-manager (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: network-manager (Ubuntu)
Assignee: Olivier Tilloy (osomon) => (unassigned)
--
You rece
See the discussion in the upstream bug report. The fix is in the master
branch and needs to be backported to the 1.10 series so that we can pick
it up in bionic.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager
Same question, will it be backported to Ubuntu 18.04 ?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1754671
Title:
Full-tunnel VPN DNS leakage regression
Status
Is it possible to upload a fixed package to bionic backports?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1754671
Title:
Full-tunnel VPN DNS leakage regression
** Changed in: network-manager
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1754671
Title:
Full-tunnel VPN DNS leakage r
A fix was merged to the upstream master branch:
https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=d9782589248e61c0cb5aec90e3eb62612891116b
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in
There's active work going on upstream (see
https://bugzilla.gnome.org/show_bug.cgi?id=746422 and
https://cgit.freedesktop.org/NetworkManager/NetworkManager/log/?h=bg
/dns-bgo746422) to fix the issue.
https://bugzilla.gnome.org/show_bug.cgi?id=746422#c36 explains how.
Once in master, it would prob
** Changed in: network-manager
Status: Unknown => Confirmed
** Changed in: network-manager
Importance: Unknown => Medium
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launch
** Bug watch added: GNOME Bug Tracker #746422
https://bugzilla.gnome.org/show_bug.cgi?id=746422
** Also affects: network-manager via
https://bugzilla.gnome.org/show_bug.cgi?id=746422
Importance: Unknown
Status: Unknown
** Changed in: network-manager (Ubuntu)
Assignee: (unassi
** Tags added: incoming rs-bb-
** Tags removed: incoming rs-bb-
** Tags added: rls-bb-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1754671
Title:
Full-
This is CVE-2018-1000135. For some reason the 'Link to CVE' option above
doesn't seem to work.
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1000135
** CVE added: https://cve.mitre.org/cgi-
bin/cvename.cgi?name=2018-1000135
--
You received this bug notification because you are a memb
*** This bug is a security vulnerability ***
Public security bug reported:
In 16.04 the NetworkManager package used to carry this patch:
http://bazaar.launchpad.net/~network-manager/network-manager/ubuntu/view/head:/debian/patches/Filter-DNS-servers-to-add-to-dnsmasq-based-on-availa.patch
It fix
Confirming this is broken. Dropping the patch 0001-dns-use-DBus-to-make-
dnsmasq-nameserver-changes.patch in network-manager
(1.2.4-0ubuntu0.16.04.1) was done, but it looks like not all the code in
that patch was actually upstream.
** Changed in: network-manager (Ubuntu)
Status: New => Conf
94 matches
Mail list logo
