This bug was fixed in the package dnsmasq - 2.79-1ubuntu0.5
---
dnsmasq (2.79-1ubuntu0.5) bionic; urgency=medium
* src/forward.c: add missing EDNS0 section. (LP: #1785383)
-- Paride Legovini Fri, 24 Sep 2021 13:05:51 +0200
** Changed in: dnsmasq (Ubuntu Bionic)
Status:
Bionic verification done according to the [Test Plan].
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
I retriggered those two tests and they passed.
--
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/1785383
Title:
missing EDNS0 record confuses systemd-resolved
Status in
Hello Steve, or anyone else affected,
Accepted dnsmasq into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/dnsmasq/2.79-1ubuntu0.5 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
The MP got reviewed and the dnsmasq upload is currently waiting in the
Bionic unapproved queue.
Being a format 1.0 package the diff [1] looks huge at first glance, but
the real changes are actually very limited (those in the MP).
[1]
MP to fix this bug in Bionic, already reviewed and uploaded:
https://code.launchpad.net/~paride/ubuntu/+source/dnsmasq/+git/dnsmasq/+merge/409149
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
I dropped the verification-* as there were about the systemd SRU, while
I'm preparing the dnsmasq one at the moment.
** Description changed:
[Impact]
- dnsmasq 2.79 and below omits EDNS0 OPT records when returning an empty answer
for a domain it is authoritative for. systemd-resolved seems to
** Changed in: dnsmasq (Ubuntu Bionic)
Status: Triaged => In Progress
--
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/1785383
Title:
missing EDNS0 record confuses
The only task that remains to tackled here is dnsmasq on Bionic.
By following the [Test Case] I verified that applying [1] fixes the bug
in Bionic. The first two hunks of the patch are already applied in the
Ubuntu package, what remains to apply is in the attached patch.
[1]
> This is related to the ubuntu server (bug) maintenance
ah, https://wiki.ubuntu.com/ServerTeam#Daily_Bug_Expiration
just part of the internal canonical server team bug tracking, got it.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
On Mon, Sep 6, 2021 at 4:05 PM Dan Streetman <1785...@bugs.launchpad.net> wrote:
>
> > [commenting so the bug doesn't get expired as we still need to look at
> the Bionic fix for dnsmasq]
>
> AFAIK, launchpad bugs only auto-expire if set to 'incomplete'. bugs set
> to anything else, like this one
> [commenting so the bug doesn't get expired as we still need to look at
the Bionic fix for dnsmasq]
AFAIK, launchpad bugs only auto-expire if set to 'incomplete'. bugs set
to anything else, like this one set to 'triaged', won't auto-expire and
don't need comments added to keep them from
[commenting so the bug doesn't get expired as we still need to look at
the Bionic fix for dnsmasq]
--
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/1785383
Title:
missing
This bug was fixed in the package systemd - 248.3-1ubuntu2
---
systemd (248.3-1ubuntu2) impish; urgency=medium
[ Kai-Heng Feng ]
* d/p/hwdb-Add-ProBook-to-use-micmute-hotkey.patch:
- Add ProBook to use micmute hotkey (LP: #1930910)
This bug was fixed in the package systemd - 237-3ubuntu10.48
---
systemd (237-3ubuntu10.48) bionic; urgency=medium
* d/p/lp1925216-seccomp-rework-functions-for-parsing-system-call-fil.patch:
Downgrade syscall group parsing failure logs to debug (LP: #1925216)
This bug was fixed in the package systemd - 246.6-1ubuntu1.4
---
systemd (246.6-1ubuntu1.4) groovy; urgency=medium
[ Andy Chi ]
*
debian/patches/lp1926547-hwdb-60-keyboard-Update-Dell-Privacy-Local-Mic-Mute-.patch
- Apply upstream patch to correct key and device mapping.
This bug was fixed in the package systemd - 245.4-4ubuntu3.7
---
systemd (245.4-4ubuntu3.7) focal; urgency=medium
[ Andy Chi ]
*
debian/patches/lp1926547-hwdb-60-keyboard-Update-Dell-Privacy-Local-Mic-Mute-.patch
- Apply upstream patch to correct key and device mapping.
This bug was fixed in the package systemd - 247.3-3ubuntu3.1
---
systemd (247.3-3ubuntu3.1) hirsute; urgency=medium
[ Andy Chi ]
*
debian/patches/lp1926547-hwdb-60-keyboard-Update-Dell-Privacy-Local-Mic-Mute-.patch
- Apply upstream patch to correct key and device mapping.
ubuntu@lp1785383-b:~$ dpkg -l systemd|grep systemd
ii systemd237-3ubuntu10.47 amd64system and service manager
ubuntu@lp1785383-b:~$ sudo systemd-resolve --reset-server-features
ubuntu@lp1785383-b:~$ sudo systemd-resolve --flush-caches
ubuntu@lp1785383-b:~$ time host test.test
ubuntu@lp1785383-f:~$ dpkg -l systemd|grep systemd
ii systemd245.4-4ubuntu3.6 amd64system and service manager
ubuntu@lp1785383-f:~$ systemd-resolve --reset-server-features
ubuntu@lp1785383-f:~$ systemd-resolve --flush-caches
ubuntu@lp1785383-f:~$ time host test.test
test.test
ubuntu@lp1785383-g:~$ dpkg -l systemd|grep systemd
ii systemd246.6-1ubuntu1.3 amd64system and service manager
ubuntu@lp1785383-g:~$ systemd-resolve --reset-server-features
ubuntu@lp1785383-g:~$ systemd-resolve --flush-caches
ubuntu@lp1785383-g:~$ time host test.test
test.test
ubuntu@lp1785383-h:~$ dpkg -l systemd|grep systemd
ii systemd247.3-3ubuntu3 amd64system and service manager
ubuntu@lp1785383-h:~$ systemd-resolve --reset-server-features
ubuntu@lp1785383-h:~$ systemd-resolve --flush-caches
ubuntu@lp1785383-h:~$ time host test.test
test.test has
Hello Steve, or anyone else affected,
Accepted systemd into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.7 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Steve, or anyone else affected,
Accepted systemd into groovy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/246.6-1ubuntu1.4 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Steve, or anyone else affected,
Accepted systemd into hirsute-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/systemd/247.3-3ubuntu3.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
@brian-murray I've merged the fix to the git repository thus it will be
part of the next upload.
** Changed in: systemd (Ubuntu Impish)
Status: Triaged => Fix Committed
** Changed in: systemd (Ubuntu Impish)
Importance: Undecided => Medium
--
You received this bug notification
marking incomplete for hirsute based on Brian's comment above.
** Changed in: systemd (Ubuntu Hirsute)
Status: In Progress => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
The SRU of systemd for Hirsute (and all its accompanying bugs) looks
good to me, but I'd like to see this fix merged for Impish at least per
SRU policy.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
** Merge proposal linked:
https://code.launchpad.net/~ddstreet/ubuntu/+source/systemd/+git/systemd/+merge/403382
--
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/1785383
** Description changed:
[Impact]
dnsmasq 2.79 and below omits EDNS0 OPT records when returning an empty answer
for a domain it is authoritative for. systemd-resolved seems to get confused by
this in certain circumstances; when using the stub resolver and requesting an
address for which
** Also affects: dnsmasq (Ubuntu Groovy)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Groovy)
Importance: Undecided
Status: New
** Also affects: dnsmasq (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Focal)
** Tags added: ddstreet
--
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/1785383
Title:
missing EDNS0 record confuses systemd-resolved
Status in systemd:
Fix Released
> although from comment #4 it sounds like it might be a regression
caused by a security fix.
it's not a security fix, it's a patch to get resolved working with specific
broken captive portals, from bug 1727237 and bug 1766969. It was proposed
upstream in this PR:
** Changed in: systemd
Status: Unknown => Fix Released
--
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/1785383
Title:
missing EDNS0 record confuses systemd-resolved
** Tags added: server-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/1785383
Title:
missing EDNS0 record confuses systemd-resolved
Status in systemd:
Unknown
I've linked to the upstream systemd bug report, although from comment #4
it sounds like it might be a regression caused by a security fix.
As to the dnsmasq patch mentioned in the issue description, what it
appears to be doing is checking if there is a pseudoheader in the
request, and if so adds
Targeting to bionic, since disco/eoan/focal are on 2.80 which, per the
OP, should already be carrying the requested fix.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
** Bug watch added: github.com/systemd/systemd/issues #9785
https://github.com/systemd/systemd/issues/9785
** Also affects: systemd via
https://github.com/systemd/systemd/issues/9785
Importance: Unknown
Status: Unknown
** Description changed:
- dnsmasq 2.79 and below omits EDNS0
** Changed in: dnsmasq (Ubuntu)
Status: Confirmed => Triaged
--
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/1785383
Title:
missing EDNS0 record confuses
Any news on this? Recent upgrade has removed my patches to dnsmasq, and
I'm hitting this again. Still convinced the Ubuntu-specific patch to
systemd-resolved is flawed as well.
I will try to get brain back into gear to have at look at this all
again. If nothing else, would be good to SRU the
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: dnsmasq (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
Returning NXDOMAIN is the behavior of Adblock on Turris-os (a derivative
of OpenWRT) with Knot resolver as back-end. I am of the same opinion
than @cbz . At the moment I will limit the logging rate.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
In my opinion the log message from system also needs to be dropped - a
number of systems will use NXDOMAIN as a means of domain blocking/ad
blocking, and this isn't thus an exceptional event that needs logging
each time.
--
You received this bug notification because you are a member of Ubuntu
Reverting the patch "resolved-Mitigate-DVE-2018-0001-by-retrying-
NXDOMAIN-with.patch" solves this problem for me. My best guess is that
the following patch segment changes some key logic:
@@ -388,12 +388,12 @@ static int dns_transaction_pick_server(DnsTransaction *t)
{
if (!server)
On further investigation this seems to be specific to the Ubuntu version
of systemd 237. I cannot reproduce it with the upstream release.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
Amend to test case:
dnsmasq -h -R -d -C /dev/null -2 $IFACE -z -i $IFACE -I lo -S /test/
--host-record=test.test,${SUBNET}.1
Cannot reproduce bug in systemd 239, but would be good to know which
commit fixed the problem for cherry picking purposes.
--
You received this bug notification because
47 matches
Mail list logo
