This bug was fixed in the package systemd - 247.3-3ubuntu3.4
---------------
systemd (247.3-3ubuntu3.4) hirsute-security; urgency=medium
* SECURITY UPDATE: DoS via DHCP FORCERENEW
- debian/patches/CVE-2020-13529.patch: tentatively ignore FORCERENEW
command in src/libsystemd-network/sd-dhcp-client.c.
- CVE-2020-13529
* SECURITY UPDATE: denial of service via stack exhaustion
- debian/patches/CVE-2021-33910.patch: do not use strdupa() on a path
in src/basic/unit-name.c.
- CVE-2021-33910
-- Marc Deslauriers <marc.deslauri...@ubuntu.com> Tue, 20 Jul 2021
07:38:18 -0400
--
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/1894622
Title:
Missing manpage for systemd-resolve
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Focal:
Fix Released
Status in systemd source package in Groovy:
Fix Released
Status in systemd source package in Hirsute:
Fix Released
Status in systemd source package in Impish:
Fix Released
Bug description:
[impact]
'man systemd-resolve' fails
[test case]
$ man systemd-resolve
No manual entry for systemd-resolve
[regression potential]
incorrect man page result for resolvectl or resolvconf, or possibly
users using deprecated systemd-resolve longer than they should
[scope]
this is needed in f and later
systemd-resolve was replaced with resolvectl between b and f, so the
man page exists in b
[other info]
the systemd-resolve binary is a symlink to the real binary resolvectl, and
users should use resolvectl for all new uses. A patch to the upstream man page
was proposed and merged in this PR:
https://github.com/systemd/systemd/pull/20064
however that is being discussed and may be reverted in this PR:
https://github.com/systemd/systemd/pull/20077
as discussed in the revert PR, it's ok for upstream to elide docs
about deprecated tooling; however distros should include deprecation
info and thus I believe it's appropriate to include the man page
symlink so users trying 'man systemd-resolve' will get the correct
'resolvectl' man page, which includes doc about how they shoudl start
using 'resolvectl' instead
[original description]
On my Focal machine there is no file /usr/share/man/man1/systemd-resolve.1.gz
This means that man systemd-resolve fails.
http://manpages.ubuntu.com/manpages/bionic/en/man1/systemd-
resolve.1.html exists and has a link on top to 20.04LTS: it points to
http://manpages.ubuntu.com/manpages/focal/en/man1/systemd-
resolve.1.html , that however 404's, and one ends up being redirected
to Bionic's.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1894622/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
