libnss-resolve treats two trailing dots on a domain name incorrectly
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
systemd |
Fix Released
|
Unknown
|
|||
systemd (Ubuntu) |
Fix Released
|
Medium
|
Martin Pitt | ||
Xenial |
Fix Released
|
Low
|
Unassigned |
Bug Description
[Impact]
libnss-resolve is an optional component not used by default in xenial. However it treats doubledot incorrectly, meaning it gets resolved when it shouldn't.
[Fix]
Cherrypick upstream patch to resolve this issue.
[Testcase]
* Enable resolve nss module
* attempt resolving www.gnu.org..
* It should fail to resolve
(base)adconrad@
208.118.235.148 STREAM wildebeest.gnu.org
208.118.235.148 DGRAM
208.118.235.148 RAW
(base)adconrad@
(base)adconrad@
(base)adconrad@
(base)adconrad@
208.118.235.148 STREAM wildebeest.gnu.org
208.118.235.148 DGRAM
208.118.235.148 RAW
(base)adconrad@
This is responsible for the new regression in glibc:
----------
FAIL: posix/tst-
original exit status 1
resolving "localhost." worked, proceeding to test
resolving "localhost.." failed, test passed
resolving "www.gnu.org." worked, proceeding to test
resolving "www.gnu.org.." worked, test failed
----------
[Regression potential]
Minimal, since this component is not used by default. However, systems that have this enabled exhibit standards non-compliant behavior. It is not expected for anybody to depend on this broken behavior.
Changed in systemd: | |
status: | Unknown → New |
Changed in systemd (Ubuntu Xenial): | |
milestone: | none → ubuntu-16.04.3 |
Changed in systemd (Ubuntu Xenial): | |
status: | Triaged → In Progress |
description: | updated |
Changed in systemd: | |
status: | New → Fix Released |
Forwarded to https:/ /github. com/systemd/ systemd/ issues/ 3978