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
thanks, marking verified
** Tags removed: verification-needed verification-needed-hirsute
** Tags added: verification-done verification-done-hirsute
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/19258
Tested systemd 247.3-3ubuntu3.2 on hirsute, without problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925827
Title:
[v247] backport routing policy rule fix
To manage notifications about this
Tested systemd 247.3-3ubuntu3.2 on hirsute, without problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925827
Title:
[v247] backport routing policy rule fix
To manage notifications about this
Hello Zhang, 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.2 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https:/
I have this queued up for hirsute, with a test build here:
https://launchpad.net/~ddstreet/+archive/ubuntu/systemd
it seems to fix the issue for me, please let me know if it doesn't work
for you, I plan to upload systemd either this week or early next week
--
You received this bug notification b
** Description changed:
+ [impact]
+
+ routing policy rules not correctly configured
+
+ [test case]
+
+ more detail in upstream bug linked from original description.
+
+ configure interface with:
+
+ [Match]
+ Name = ens3
+
+ [Network]
+ Address = 10.0.0.1/32
+
+ [RoutingPolicyRule]
+ Fami
** Changed in: systemd (Ubuntu Hirsute)
Assignee: (unassigned) => Zhang Youfu (zhangyoufu)
** Changed in: systemd (Ubuntu Hirsute)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
> I'm able to reproduce this on hirsute, but not groovy, so this seems to
> affect only hirsute; please correct me if that's wrong.
That’s correct.
> only 'networkctl reload' doesn't work, normal systemd-networkd startup works
`systemctl restart systemd-networkd` doesn’t work either.
--
You rec
I'm able to reproduce this on hirsute, but not groovy, so this seems to
affect only hirsute; please correct me if that's wrong.
Due to the rather large size of the patch to fix this, and the very low
impact (only 'networkctl reload' doesn't work, normal systemd-networkd
startup works), I think it'
The attachment "96.patch" seems to be a patch. If it isn't, please
remove the "patch" flag from the attachment, remove the "patch" tag, and
if you are a member of the ~ubuntu-reviewers, unsubscribe the team.
[This is an automated message performed by a Launchpad user owned by
~brian-murray, for a
11 matches
Mail list logo
