| 2023-02-10 21:05:27 |
rwruck |
bug |
|
|
added bug |
| 2023-02-13 19:00:08 |
Lena Voytek |
nominated for series |
|
Ubuntu Jammy |
|
| 2023-02-13 19:00:08 |
Lena Voytek |
bug task added |
|
bind9 (Ubuntu Jammy) |
|
| 2023-02-13 19:00:14 |
Lena Voytek |
bind9 (Ubuntu): status |
New |
Fix Released |
|
| 2023-02-13 19:00:17 |
Lena Voytek |
bind9 (Ubuntu Jammy): status |
New |
In Progress |
|
| 2023-02-13 19:00:19 |
Lena Voytek |
bind9 (Ubuntu Jammy): assignee |
|
Lena Voytek (lvoytek) |
|
| 2023-02-13 19:00:47 |
Lena Voytek |
nominated for series |
|
Ubuntu Lunar |
|
| 2023-02-13 19:00:47 |
Lena Voytek |
bug task added |
|
bind9 (Ubuntu Lunar) |
|
| 2023-02-13 22:07:32 |
Lena Voytek |
merge proposal linked |
|
https://code.launchpad.net/~lvoytek/ubuntu/+source/bind9/+git/bind9/+merge/437223 |
|
| 2023-03-08 20:41:37 |
Lena Voytek |
description |
Ubuntu release: 22.04.1 LTS (jammy) amd64
bind9 version: 1:9.18.1-1ubuntu1.3
bind9 comes with the plugins filter-a.so and filter-aaaa.so preinstalled into /usr/lib/x86_64-linux-gnu/bind/.
When trying to actually use them, bind9 fails to start:
loading plugin '/usr/lib/x86_64-linux-gnu/named/filter-aaaa.so'
failed to dlopen() plugin '/usr/lib/x86_64-linux-gnu/named/filter-aaaa.so': /usr/lib/x86_64-linux-gnu/named/filter-aaaa.so: cannot open shared object file: No such file or directory
Looks like either bind9 is configured with a wrong plugin path or the files got dropped into the wrong directory.
To reproduce, add the following to /etc/bind/named.conf.options and restart:
plugin query "filter-aaaa.so" {
filter-aaaa-on-v4 yes;
};
Workaround: Use the full path like in
plugin query "/usr/lib/x86_64-linux-gnu/bind/filter-aaaa.so" {
filter-aaaa-on-v4 yes;
}; |
[Impact]
When a user provides the name of an existing bind9 plugin to /etc/bind/named.conf.options, it fails to recognize it. This is because named is searching in the wrong folder - /usr/lib/x86_64-linux-gnu/named/ instead of the correct location /usr/lib/x86_64-linux-gnu/bind/.
This fix should be added to Jammy to maintain the correct behavior for named plugin configurations.
The fix will be provided by the minor release update described in (LP: #2003586)
[Test Plan]
# lxc launch images:ubuntu/jammy test-bind9
# lxc exec test-bind9 bash
# apt update && apt dist-upgrade
# apt install bind9
# cat <<EOF >/etc/bind/named.conf.options
options {
directory "/var/cache/bind";
dnssec-validation auto;
listen-on-v6 { any; };
};
plugin query "filter-aaaa.so" {
filter-aaaa-on-v4 yes;
};
EOF
# named-checkconf
- Before the update this fails since named is looking for filter-aaaa.so in /usr/lib/x86_64-linux-gnu/named instead of the correct location /usr/lib/x86_64-linux-gnu/bind. After the fix named-checkconf succeeds.
[Where problems could occur]
Problems can occour in multiple areas outside of this fix since it will be a part of a minor release update. However, issues directly associated with this fix would likely arise in plugin activation, which can be checked using named-checkconf.
[Other Info]
The fix for this issue exists in Kinetic prior to its equivalent minor release update.
[Original Description]
Ubuntu release: 22.04.1 LTS (jammy) amd64
bind9 version: 1:9.18.1-1ubuntu1.3
bind9 comes with the plugins filter-a.so and filter-aaaa.so preinstalled into /usr/lib/x86_64-linux-gnu/bind/.
When trying to actually use them, bind9 fails to start:
loading plugin '/usr/lib/x86_64-linux-gnu/named/filter-aaaa.so'
failed to dlopen() plugin '/usr/lib/x86_64-linux-gnu/named/filter-aaaa.so': /usr/lib/x86_64-linux-gnu/named/filter-aaaa.so: cannot open shared object file: No such file or directory
Looks like either bind9 is configured with a wrong plugin path or the files got dropped into the wrong directory.
To reproduce, add the following to /etc/bind/named.conf.options and restart:
plugin query "filter-aaaa.so" {
filter-aaaa-on-v4 yes;
};
Workaround: Use the full path like in
plugin query "/usr/lib/x86_64-linux-gnu/bind/filter-aaaa.so" {
filter-aaaa-on-v4 yes;
}; |
|
| 2023-03-17 17:21:08 |
Steve Langasek |
bind9 (Ubuntu Jammy): status |
In Progress |
Fix Committed |
|
| 2023-03-17 17:21:09 |
Steve Langasek |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2023-03-17 17:21:11 |
Steve Langasek |
bug |
|
|
added subscriber SRU Verification |
| 2023-03-17 17:21:15 |
Steve Langasek |
tags |
|
verification-needed verification-needed-jammy |
|
| 2023-03-22 22:38:37 |
Lena Voytek |
tags |
verification-needed verification-needed-jammy |
verification-done verification-done-jammy |
|
| 2023-03-29 03:35:53 |
Launchpad Janitor |
bind9 (Ubuntu Jammy): status |
Fix Committed |
Fix Released |
|
| 2023-03-29 03:35:53 |
Launchpad Janitor |
cve linked |
|
2022-1183 |
|
| 2023-03-29 03:35:53 |
Launchpad Janitor |
cve linked |
|
2022-2795 |
|
| 2023-03-29 03:35:53 |
Launchpad Janitor |
cve linked |
|
2022-2881 |
|
| 2023-03-29 03:35:53 |
Launchpad Janitor |
cve linked |
|
2022-2906 |
|
| 2023-03-29 03:35:53 |
Launchpad Janitor |
cve linked |
|
2022-3080 |
|
| 2023-03-29 03:35:53 |
Launchpad Janitor |
cve linked |
|
2022-3094 |
|
| 2023-03-29 03:35:53 |
Launchpad Janitor |
cve linked |
|
2022-3736 |
|
| 2023-03-29 03:35:53 |
Launchpad Janitor |
cve linked |
|
2022-38178 |
|
| 2023-03-29 03:35:53 |
Launchpad Janitor |
cve linked |
|
2022-3924 |
|
| 2023-03-29 03:36:32 |
Chris Halse Rogers |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
