Maybe this test is good.
With current disco packages:
$ delv +dnssec +multiline @127.0.0.1 ed25519.nl
;; validating ed25519.nl/A: no valid signature found
; unsigned answer
ed25519.nl. 3591 IN A 77.72.150.82
ed25519.nl. 3200171710 IN RRSIG A 15 2 3600 (
Do you have an example at hand of such a breakage? It will make the
testing and SRU easier. Something like using dig with @localhost and
asking for info for such a public zone.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to bind9 in
Thanks for filing this bug in Ubuntu.
You are right, this should have been enabled back.
** Changed in: bind9 (Ubuntu)
Status: New => Triaged
** Changed in: bind9 (Ubuntu)
Importance: Undecided => Medium
** Also affects: bind9 (Ubuntu Disco)
Importance: Undecided
Status:
Thanks, please keep us posted.
2.9: security fix (CVE-2019-3880)
2.8: made new API call available (bug #1778322)
2.7: memleak fix (bug #1814532)
2.6: smbc_opendir should not return EEXIST with invalid login credentials(bug
#1801227)
** CVE added:
Thanks for filing this bug in Ubuntu.
This is the error that was reported:
ERROR: Unable to start MySQL server:
mysqld: Can't read dir of '/etc/mysql/conf.d/' (Errcode: 2 - No such file or
directory)
That is a very core directory of mysql, and it shouldn't have gone missing.
Maybe you removed
It worked just fine on a disco desktop default install.
I brought up a bionic vm, which has samba running and set to a workgroup
called "workgroup" and has a /pub share. On disco, I click on "other
locations", then "windows network", and I see "WORKGROUP". I can click
on "WORKGROUP", which then
I checked disco when I prepared these updates for bionic and cosmic, and
it was allright. Let me re-check with a default install using the CD
this time, now that it is released.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to samba in