resolved incorrectly limits TCP reply to edns0 payload
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
| systemd (Ubuntu) |
Undecided
|
Unassigned | ||
| Bionic |
Medium
|
Dan Streetman | ||
| Disco |
Medium
|
Dan Streetman | ||
| Eoan |
Medium
|
Dan Streetman |
Bug Description
[impact]
glibc's getaddrinfo() uses EDNS0 to talk to resolved, and it sets its payload limit to 1200. When the response is larger than 1200, resolved will limit the response and set the truncate flag. This causes getaddrinfo() to switch to TCP and request again, but glibc incorrectly keeps the EDNS0 RR opt, with the same 1200 payload limit. Most dns nameservers ignore EDNS0 payload limit for TCP, since per RFC it applies only to UDP, but resolved does not and again marks the response as truncated. This prevents getaddrinfo() from being able to resolve any records with a response over 1200 bytes.
[test case]
use ping or telnet, which use getaddrinfo(), to lookup an A record with a lot of results, like toomany100.
$ telnet toomany100.
telnet: could not resolve toomany100.
[regression potential]
any regression would likely result in failure to correctly lookup a hostname or to provide the correct response to a local client.
[other info]
note that on Bionic, this also requires backporting TCP pipelining support in the stub resolver.
Changed in systemd (Ubuntu Eoan): | |
status: | New → Fix Released |
Changed in systemd (Ubuntu Disco): | |
status: | New → In Progress |
Changed in systemd (Ubuntu Bionic): | |
status: | New → In Progress |
Changed in systemd (Ubuntu Disco): | |
importance: | Undecided → Medium |
Changed in systemd (Ubuntu Bionic): | |
importance: | Undecided → Medium |
Changed in systemd (Ubuntu Eoan): | |
importance: | Undecided → Medium |
assignee: | nobody → Dan Streetman (ddstreet) |
Changed in systemd (Ubuntu Disco): | |
assignee: | nobody → Dan Streetman (ddstreet) |
Changed in systemd (Ubuntu Bionic): | |
assignee: | nobody → Dan Streetman (ddstreet) |
Changed in systemd (Ubuntu): | |
status: | New → Fix Released |
tags: | added: bionic ddstreet disco eoan systemd |
tags: | removed: eoan |
description: | updated |
Changed in systemd (Ubuntu Disco): | |
status: | In Progress → Fix Committed |
tags: | added: verification-needed verification-needed-disco |
All autopkgtests for the newly accepted systemd (240-6ubuntu5.8) for disco have finished running.
The following regressions have been reported in tests triggered by the package:
prometheus-
php7.2/
gvfs/1.
pdns-recursor/
webhook/unknown (armhf)
munin/2.
systemd/
Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUp
https:/
[1] https:/
Thank you!
Hello Dan, or anyone else affected,
Accepted systemd into bionic-proposed. The package will build now and be available at https:/
Please help us by testing this new package. See https:/
If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-
Further information regarding the verification process can be found at https:/
N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.
Changed in systemd (Ubuntu Bionic): | |
status: | In Progress → Fix Committed |
tags: | added: verification-needed-bionic |
Dan Streetman (ddstreet) wrote : | #4 |
ubuntu@
ii systemd 240-6ubuntu5.7 amd64 system and service manager
ubuntu@
telnet: could not resolve toomany100.
ubuntu@
ii systemd 240-6ubuntu5.8 amd64 system and service manager
ubuntu@
Trying 10.254.201.100...
tags: |
added: verification-done-disco removed: verification-needed-disco |
All autopkgtests for the newly accepted systemd (237-3ubuntu10.32) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:
gvfs/1.
linux/unknown (ppc64el)
Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUp
https:/
[1] https:/
Thank you!
Dan Streetman (ddstreet) wrote : | #6 |
ubuntu@
ii systemd 237-3ubuntu10.31 amd64 system and service manager
ubuntu@
telnet: could not resolve toomany100.
ubuntu@
ii systemd 237-3ubuntu10.32 amd64 system and service manager
ubuntu@
Trying 10.254.201.100...
tags: |
added: verification-done verification-done-bionic removed: verification-needed verification-needed-bionic |
Hello Dan, or anyone else affected,
Accepted systemd into bionic-proposed. The package will build now and be available at https:/
Please help us by testing this new package. See https:/
If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-
Further information regarding the verification process can be found at https:/
N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.
tags: |
added: verification-needed verification-needed-bionic removed: verification-done verification-done-bionic |
All autopkgtests for the newly accepted systemd (237-3ubuntu10.33) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:
gvfs/1.
dovecot/
umockdev/0.11.1-1 (ppc64el)
Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUp
https:/
[1] https:/
Thank you!
Dan Streetman (ddstreet) wrote : | #9 |
ubuntu@
ii systemd 237-3ubuntu10.31 amd64 system and service manager
ubuntu@
telnet: could not resolve toomany100.
ubuntu@
ii systemd 237-3ubuntu10.33 amd64 system and service manager
ubuntu@
Trying 10.254.201.100...
tags: |
added: verification-done verification-done-bionic removed: verification-needed verification-needed-bionic |
Launchpad Janitor (janitor) wrote : | #10 |
This bug was fixed in the package systemd - 240-6ubuntu5.8
---------------
systemd (240-6ubuntu5.8) disco; urgency=medium
[ Victor Tapia ]
* d/p/resolved_
Fix regression introduced by
resolved-
DNSSEC=yes (LP: #1796501)
[ Dan Streetman ]
* d/p/lp1840640-
allow sync_file_range2 in nspawn container (LP: #1840640)
* d/p/lp1847527-
do not request Content-Length if Transfer-Encoding is chunked
(LP: #1847527)
* d/t/storage: fix flaky test
(LP: #1847815)
* d/p/lp1843381-
debian/
fix rename delay for systems using "Dell MAC passthrough"
(LP: #1843381)
* d/p/lp1849733/
d/p/
ignore EDNS0 payload limit when responding over TCP (LP: #1849733)
* d/p/lp1849658-
- Fix bug in refcounting TCP stream types (LP: #1849658)
* d/extra/
- only restart resolved if dhclient conf changed (LP: #1805183)
[ Balint Reczey ]
* d/p/test-
fix test breakage due to running in nested lxd container
(LP: #1845337)
-- Dan Streetman <email address hidden> Fri, 04 Oct 2019 09:06:58 -0400
Changed in systemd (Ubuntu Disco): | |
status: | Fix Committed → Fix Released |
The verification of the Stable Release Update for systemd 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 encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
Launchpad Janitor (janitor) wrote : | #12 |
This bug was fixed in the package systemd - 237-3ubuntu10.33
---------------
systemd (237-3ubuntu10.33) bionic; urgency=medium
* d/p/lp1852754/
d/p/
d/p/
- Complete link setup after setting mtu (LP: #1852754)
systemd (237-3ubuntu10.32) bionic; urgency=medium
[ Victor Tapia ]
* d/p/resolved_
Fix regression introduced by
resolved-
DNSSEC=yes (LP: #1796501)
[ Dan Streetman ]
* d/p/fix-
- Fix typo in previous patch
* d/p/lp1840640-
- allow sync_file_range2 in nspawn container
(LP: #1840640)
* d/p/lp1783994-
- avoid systemd-
(LP: #1783994)
* d/p/lp1832672-
- do not fail entire file on error when parsing /etc/hosts
- parse # char anywhere in line as start of comment
(LP: #1832672)
* d/p/lp1843381-
debian/
- fix rename delay for systems using "Dell MAC passthrough"
(LP: #1843381)
* d/p/lp1849733/
d/p/
d/p/
d/p/
d/p/
d/p/
d/p/
d/p/
d/p/
d/p/
d/p/
d/p/
d/p/
- add TCP pipelining to handle getaddrinfo() fallback to TCP
- ignore EDNS0 payload limit when responding over TCP (LP: #1849733)
* d/p/lp1849658-
- Fix bug in refcounting TCP stream types (LP: #1849658)
* d/p/lp1850704/
d/p/
- Fix setting mtu if interface already up (LP: #1850704)
* d/extra/
- only restart resolved if dhclient conf changed (LP: #1805183)
-- Dan Streetman <email address hidden> Fri, 15 Nov 2019 10:01:16 -0500
Changed in systemd (Ubuntu Bionic): | |
status: | Fix Committed → Fix Released |
Hello Dan, or anyone else affected,
Accepted systemd into disco-proposed. The package will build now and be available at https:/ /launchpad. net/ubuntu/ +source/ systemd/ 240-6ubuntu5. 8 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https:/ /wiki.ubuntu. com/Testing/ EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification- needed- disco to verification- done-disco. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed- disco. In either case, without details of your testing we will not be able to proceed.
Further information regarding the verification process can be found at https:/ /wiki.ubuntu. com/QATeam/ PerformingSRUVe rification . Thank you in advance for helping!
N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.