This bug was fixed in the package systemd - 237-3ubuntu10.52
---
systemd (237-3ubuntu10.52) bionic; urgency=medium
* d/extra/dhclient-enter-resolved-hook:
Reset start limit counter for systemd-resolved in dhclient hook
(LP: #1939255)
https://git.launchpad.net/~ubuntu-co
root@lp1853164-b:~# dpkg -l systemd|grep systemd
ii systemd237-3ubuntu10.51 amd64system and service manager
root@lp1853164-b:~# dpkg -l | grep -E 'ifupdown|resolvconf'
ii ifupdown 0.8.17ubuntu1.1 amd64
high level tools to configu
heh, please ignore the above comment, the current focal systemd was
respun, but the fix for this was already released for focal, this only
needs bionic verified now :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
as systemd was respun due to bug 1942899, and only the one udev (hwdb)
patch was reverted which shouldn't affect this at all, I'm remarking
this as verified still based on testing for the previous version above.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Hello Mason, or anyone else affected,
Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.52 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://
This bug was fixed in the package systemd - 245.4-4ubuntu3.10
---
systemd (245.4-4ubuntu3.10) focal-security; urgency=medium
* SECURITY UPDATE: DoS via DHCP FORCERENEW
- debian/patches/CVE-2020-13529.patch: tentatively ignore FORCERENEW
command in src/libsystemd-network/sd
marking as verified for focal based on above feedback
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
FWIW, the fix in focal-proposed looks good on my end as well.
I can confirm that the /etc/dhcp/dhclient-enter-hooks.d/resolved script
now has the is-enabled check, and while I won't be able to test out
resolvconf, I regard the updated conditional as equivalent to my
previous known-good workaround
I've tested this, and under the noted conditions resolvconf no longer
has an issue updating /etc/resolv.conf. Thank you for your time and
attention to detail!
Unless someone else weighs in noting a problem, from my perspective it
seems like this bug can be closed now, as you've corrected the issue
Hey there. Thanks for your time on this. I'll try to supply positive
confirmation over the weekend.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853164
Title:
systemd: /etc/dhcp/dhclient-enter-hoo
Hello Mason, 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.8 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://w
** Also affects: systemd (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu Bionic)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
My staging ppa has the 'next' version that i'll be uploading soon
(possibly with other patches), if you want to test it to verify it does
fix this for you:
https://launchpad.net/~ddstreet/+archive/ubuntu/systemd
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Thank you @ddstreet, I'm happy to see this as well. I'd like to get rid
of the workaround I've been using for this issue:
# dpkg-divert --divert /etc/dhcp/dhclient-enter-
hooks.d/resolved.DISABLED --rename /etc/dhcp/dhclient-enter-
hooks.d/resolved
--
You received this bug notification because y
@ddstreet
Thank you! It has been a long time coming, so I'm glad to see this
fixed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853164
Title:
systemd: /etc/dhcp/dhclient-enter-hooks.d/resolved e
** Changed in: systemd (Ubuntu Focal)
Assignee: (unassigned) => Dan Streetman (ddstreet)
** Changed in: systemd (Ubuntu Focal)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
@lixo-geeksmith I have the patch for this queued up for the next systemd
upload, sorry for the long delay.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853164
Title:
systemd: /etc/dhcp/dhclient-en
@thayne-u
They don't care. There is ample reason to implement a fix for this, but
they refuse to do what's best for users because they don't want us to
run any software that doesn't start with "systemd". This is a very
simple bug with a very simple fix, but they refuse to fix their defects.
I've
> If you know of specific problems with it, we can best help you (and
all other Ubuntu users) if you give us bug reports for those problems.
There's this: https://github.com/systemd/systemd/issues/5755
Also, systemd-resolved does not have an equivalent of dnsmasq's "all-
servers" option, which I
** Description changed:
- The functionality exists to allow users to revert to the traditional ifupdown
- package for network configuration. Alongside this, systemd's often-buggy
+ [impact]
+
+ with systemd-resolved disabled, dhclient doesn't correctly notify
+ resolvconf about dns server(s)
+
bug 1890609 removed the hook script from systemd (by moving it into the
isc-dhcp package)
** Changed in: systemd (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
** Tags removed: ddstreet
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853164
Title:
systemd: /etc/dhcp/dhclient-enter-hooks.d/resolved error
To manage notifications about this bug go to:
https:/
** Merge proposal linked:
https://code.launchpad.net/~vorlon/ubuntu/+source/ifupdown/+git/ifupdown/+merge/382729
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853164
Title:
systemd: /etc/dhcp/d
** Tags added: ddstreet
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853164
Title:
systemd: /etc/dhcp/dhclient-enter-hooks.d/resolved error
To manage notifications about this bug go to:
https://b
** Tags added: resolved-resolvconf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853164
Title:
systemd: /etc/dhcp/dhclient-enter-hooks.d/resolved error
To manage notifications about this bug go to
For Ubuntu 20.04, resolvconf will not be allowed to manage
/etc/resolv.conf, this will always be managed via systemd-resolved. So
while you're right that this is a bug in the hook, it will not be a
priority to fix since the code will be rewritten and replaced.
> Alongside this, systemd's often-bu
I thought we were going to some effort to reduce the number of systems
where resolveconf was going to be used, or even remove it from the
distro entirely.
Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
Interesting. But the code is still incorrect, with my patch correcting it,
so I guess we'll see how it goes. I can either fix it locally or go elsewhere,
but I'm hoping it's simply fixed in the distribution.
Thanks for the pointer.
--
You received this bug notification because you are a member
I think this is a dup of bug 1745463, which might not be the answer you
were hoping for.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853164
Title:
systemd: /etc/dhcp/dhclient-enter-hooks.d/resolv
** Also affects: systemd (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu Focal)
Status: New => Triaged
** Changed in: systemd (Ubuntu Focal)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
The attachment "Check for active service, not existence of binary."
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 La
** Tags added: rls-ff-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853164
Title:
systemd: /etc/dhcp/dhclient-enter-hooks.d/resolved error
To manage notifications about this bug go to:
ht
sdezial notes this being terser. I do the long form out of superstitious awe
at the notion of a return code of zero being "true", even though it always
is, but this would be terser and also correct:
if systemctl is-active systemd-resolved > /dev/null 2>&1; then
--
You received this bug notif
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853164
Title:
systemd: /etc/dhcp/dhclient-enter-hooks.d/resolved error
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/
34 matches
Mail list logo
