You are correct that the multicast support has been removed in NTPsec.
This was intentional:
https://docs.ntpsec.org/latest/ntpsec.html
"Broadcast- and multicast modes, which are impossible to secure, have been
removed."
The Debian maintainers of the "ntp" package decided to stop maintaining
I was able to verify this is fixed in iputils-ping 20210202-1. That is,
I saw this same problem, grabbed those sources from Debian, built them,
and tested again. Accordingly, this should already be fixed in Ubuntu
impish.
--
You received this bug notification because you are a member of Ubuntu
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/1908473
Title:
rsyslog-relp: imrelp module leaves
I tested this on Focal. I installed librelp0 and restart rsyslog. Prior
to the change, sockets were stacking up in CLOSE-WAIT (both from normal
use and from the netcat test). After the change, sockets are being
closed correctly.
** Tags removed: verification-needed-focal
** Tags added:
The test package fixes the issue for me.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/1908473
Title:
rsyslog-relp: imrelp module leaves sockets in CLOSE_WAIT state
First I reverted isc-dhcp-server back to the original focal version, since I
had an updated version from the PPA:
$ sudo apt install isc-dhcp-server=4.4.1-2.1ubuntu5
isc-dhcp-common=4.4.1-2.1ubuntu5
Then I install the update packages:
$ sudo apt update
$ sudo apt install
Andrew, 1:9.11.16+dfsg-3~build1 is wrong. The correct version is
1:9.11.16+dfsg-3~ubuntu1 (~ubuntu1 instead of ~build1).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
Excellent. I'm available to test the -proposed update for focal whenever
it is ready.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1872118
Title:
[SRU] DHCP Cluster
Jorge, I agree with Gianfranco Costamagna that a rebuild of isc-dhcp is
NOT required. Why do you think it is?
Presumably BIND also uses these libraries? If so, it seems like the Test
Case should involve making sure BIND still seems to work, and that BIND
should be mentioned in the Regression
No crashes to report.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1872118
Title:
DHCP Cluster crashes after a few hours
Status in DHCP:
New
Status in bind9-libs
Jorge, it sounds like ISC might think there is a more fundamental issue here:
https://gitlab.isc.org/isc-projects/dhcp/-/issues/121#note_152804
** Bug watch added: gitlab.isc.org/isc-projects/dhcp/-/issues #121
https://gitlab.isc.org/isc-projects/dhcp/-/issues/121
--
You received this bug
Jorge, I have been running for 25 hours on the patched version with no
crashes on either server.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1872118
Title:
DHCP
I ran:
sudo apt install \
isc-dhcp-server=4.4.1-2.1ubuntu6~ppa1 \
libdns-export1109=1:9.11.16+dfsg-3~ppa1 \
libirs-export161=1:9.11.16+dfsg-3~ppa1 \
libisc-export1105=1:9.11.16+dfsg-3~ppa1 && \
sudo systemctl restart isc-dhcp-server
The restart at the end was just for
** Bug watch added: gitlab.isc.org/isc-projects/dhcp/issues #128
https://gitlab.isc.org/isc-projects/dhcp/issues/128
** Also affects: dhcp via
https://gitlab.isc.org/isc-projects/dhcp/issues/128
Importance: Unknown
Status: Unknown
--
You received this bug notification because
I was able to reproduce this with 4.4.2 plus the Ubuntu packaging. I did
not try with stock 4.4.2 from source.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1872118
Public bug reported:
rsyslogd: error during parsing file /etc/rsyslog.d/FILENAME.conf, on or
before line 22: imrelp: librelp does not support input parameter
'tls.tlscfgcmd'; it probably is too old (1.5.0 or higher should be
fine); ignoring setting now. [v8.2001.0 try
I have confirmed that the fix in -proposed fixes the issue for me.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to kmod in Ubuntu.
https://bugs.launchpad.net/bugs/1872863
Title:
QEMU/KVM display is garbled when booting
Currently, addresses is a "sequence of scalars" (aka a list). Here is
the example from the Netplan reference you quoted:
addresses: [192.168.14.2/24, "2001:1::1/64"]
This can, currently, also be written in this form (quotes optional):
addresses:
- 192.168.14.2/24
- "2001:1::1/64"
I actually
I was able to verify this on Bionic:
rlaager@bison:~$ ip -6 route show
2600:2600::/64 dev ens3 proto kernel metric 256 pref medium
fe80::/64 dev ens3 proto kernel metric 256 pref medium
default via 2600:2600::254 dev ens3 proto static metric 1024 pref medium
rlaager@bison:~$ sudo apt update
...
I was an affected user. I have confirmed that the package from bionic-
proposed works. I do not have any systems installed with Cosmic.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Attached is an updated version of the patch that builds. The previous
one was failing because there's a test case that makes sure an "insert
2" of an IPv6 rule fails. That's enforcing the existence of the behavior
that here we are arguing is a bug.
** Patch added: "Updated patch"
Taking into account the two proposed patches, and what I believe the
code to be doing, attached is a patch I believe is suitable for
inclusion.
** Patch added: "0005-lp1368411.patch"
https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1368411/+attachment/5198539/+files/0005-lp1368411.patch
--
I'm seeing the same errors with NTPsec (a fork of this ntpd, which I
have packaged for Debian) on 16.04. The apparmor policy is copied from
this ntp package. I'm not able to reproduce the problem at will, but it
seems to happen regularly. The proposed change seems to have resolved
it.
--
You
Does ZFS actually have any translations? There are no .po files in the
source and no .mo files in the binary package.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sysvinit in Ubuntu.
https://bugs.launchpad.net/bugs/1607920
This is fixed in 16.10. Is there a plan to backport this? I'm guessing
not, because of the risk of regressions. If there's no plans to SRU,
then this bug should probably be closed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
I don't see how turning on a new feature is a bug.
** Changed in: e2fsprogs (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu.
https://bugs.launchpad.net/bugs/1601997
The fix was merged upstream here:
https://github.com/zfsonlinux/zfs/commit/792517389fad5c495a2738b61c2e9c65dedaaa9a
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sysvinit in Ubuntu.
https://bugs.launchpad.net/bugs/1607920
The package from proposed works. I tested version 0.8.10ubuntu1.1. The
diff looks correct.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in
I did not forward it. I sometimes do, sometimes don't, depending on a
lot of factors. In this case, even though I assumed it would affect
Debian, I was hesitant to claim the existence of a high priority bug if
I hadn't personally verified it.
--
You received this bug notification because you are
** Patch added: "A fix for yakkety"
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1618726/+attachment/4731336/+files/ifupdown-fix-1618726-yakkety.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown
** Patch added: "A fix for xenial"
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1618726/+attachment/4731337/+files/ifupdown-fix-1618726-xenial.debdiff
** Description changed:
- This is a trivially reproducible crash in ifup/ifdown.
+ This is a trivially reproducible crash in
Public bug reported:
This is a trivially reproducible crash in ifup/ifdown.
Steps to reproduce:
1) echo no-scripts foo bar >> /etc/network/interfaces
2) ifup baz
Expected results:
Unknown interface baz
Actual results:
Segmentation fault (core dumped)
It's irrelevant whether the second
chiluk is looking to work on this for upstream. I might jump in too.
https://github.com/zfsonlinux/zfs/issues/4680
** Bug watch added: Github Issue Tracker for ZFS #4680
https://github.com/zfsonlinux/zfs/issues/4680
--
You received this bug notification because you are a member of Ubuntu
I might be overstepping here, but I'm marking this as Fix Released. I
can confirm, as with comment #16, that this is no longer an issue. I'm
on Vivid.
** Changed in: sudo (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
AFAIK, Sun Java is no longer in Ubuntu. Even if it is, it's probably a
new version than 6. I'm sure this is broken, but nobody is going to fix
it. I just don't care any more.
** Changed in: sun-java6 (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you
** Changed in: help2man (Ubuntu)
Status: Triaged => Invalid
** Changed in: help2man
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to coreutils in Ubuntu.
This has been fixed in at least Ubuntu vivid.
** Changed in: rsync (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsync in Ubuntu.
https://bugs.launchpad.net/bugs/479405
Public bug reported:
[Title copied from Debian bug, which was not filed by me. Description
below is mine.]
If an NTP client sends a request with a source port less than 123, the
packet is silently ignored by ntpd. This is occurring in our environment
due to NAT.
Attached is the patch already
38 matches
Mail list logo
