| 2022-08-29 14:13:37 |
trya uuum |
bug |
|
|
added bug |
| 2022-08-29 14:14:16 |
trya uuum |
description |
in unbound config one of the valid ways to specify IPs to listen on is to specify an interface name. e.g.
```
server:
interface: lan0
```
unbound starts and works correctly, but unbound-checkconf returns an error:
```
# unbound-checkconf
[1661781808] unbound-checkconf[4362:0] fatal error: cannot parse interface specified as 'lan0'
```
this bug was fixed upstream https://github.com/NLnetLabs/unbound/issues/574 |
in unbound config one of the valid ways to specify IPs to listen on is to specify an interface name. e.g.
```
server:
interface: lan0
```
unbound starts and works correctly, but unbound-checkconf returns an error:
```
# unbound-checkconf
[1661781808] unbound-checkconf[4362:0] fatal error: cannot parse interface specified as 'lan0'
```
this bug was fixed upstream https://github.com/NLnetLabs/unbound/issues/574 but it's still present in ubuntu 22.04 |
|
| 2022-08-30 19:02:06 |
Lucas Kanashiro |
nominated for series |
|
Ubuntu Jammy |
|
| 2022-08-30 19:02:06 |
Lucas Kanashiro |
bug task added |
|
unbound (Ubuntu Jammy) |
|
| 2022-08-30 19:02:14 |
Lucas Kanashiro |
unbound (Ubuntu): status |
New |
Fix Released |
|
| 2022-08-30 19:02:18 |
Lucas Kanashiro |
unbound (Ubuntu Jammy): status |
New |
Triaged |
|
| 2022-08-30 19:03:45 |
Lucas Kanashiro |
bug |
|
|
added subscriber Ubuntu Server |
| 2022-08-30 19:03:48 |
Lucas Kanashiro |
tags |
|
server-todo |
|
| 2022-09-07 15:23:03 |
Lena Voytek |
unbound (Ubuntu Jammy): assignee |
|
Lena Voytek (lvoytek) |
|
| 2022-09-07 15:23:07 |
Lena Voytek |
unbound (Ubuntu Jammy): status |
Triaged |
In Progress |
|
| 2022-09-12 17:07:50 |
Lena Voytek |
description |
in unbound config one of the valid ways to specify IPs to listen on is to specify an interface name. e.g.
```
server:
interface: lan0
```
unbound starts and works correctly, but unbound-checkconf returns an error:
```
# unbound-checkconf
[1661781808] unbound-checkconf[4362:0] fatal error: cannot parse interface specified as 'lan0'
```
this bug was fixed upstream https://github.com/NLnetLabs/unbound/issues/574 but it's still present in ubuntu 22.04 |
[Impact]
When a user attempts to run unbound-checkconf and any of their stated interfaces matches the name of an existing network interface, the program will crash and will be unable to verify the configuration.
For example, if an unbound configuration file contains something like
server:
interface: lan0
or
server:
interface: lo
and so on, unbound-checkconf will crash.
This fix should be added to Jammy so configuration files and network interfaces can be properly validated for unbound.
The bug was fixed by adding a few commits from upstream as patches to unbound-checkconf. A function in unbound-checkconf.c was modified to resolve the interface name and check
that it works correctly. Meanwhile a commit that modifies the function resolve_interface_names in listen_dnsport.c and its calls was added as a patch to allow interface resolution to work correctly.
[Test Plan]
The following test can be used to reproduce the error:
# lxc launch images:ubuntu/jammy test-unbound
# lxc exec test-unbound bash
# apt update && apt dist-upgrade -y
# apt install unbound -y
# echo "
server:
interface: lo" >> /etc/unbound/unbound.conf
# unbound-checkconf
[Where problems could occur]
Since the resolve_interface_names function had to be updated for the unbound-checkconf to work, the places where it is called in the unbound package also had to be modified. This could lead to changes in behavior within unbound-control and the unbound daemon when checking interface names. Although this function will match the behavior upstream and in Kinetic, commits related to the handling of this function may be missed by the patch files.
[Other Info]
The issue was fixed upstream and was fixed in Kinetic through the most recent merge into Ubuntu.
[Original Description]
in unbound config one of the valid ways to specify IPs to listen on is to specify an interface name. e.g.
```
server:
interface: lan0
```
unbound starts and works correctly, but unbound-checkconf returns an error:
```
# unbound-checkconf
[1661781808] unbound-checkconf[4362:0] fatal error: cannot parse interface specified as 'lan0'
```
this bug was fixed upstream https://github.com/NLnetLabs/unbound/issues/574 but it's still present in ubuntu 22.04 |
|
| 2022-09-12 17:21:14 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~lvoytek/ubuntu/+source/unbound/+git/unbound/+merge/429771 |
|
| 2022-09-16 14:27:41 |
Lena Voytek |
description |
[Impact]
When a user attempts to run unbound-checkconf and any of their stated interfaces matches the name of an existing network interface, the program will crash and will be unable to verify the configuration.
For example, if an unbound configuration file contains something like
server:
interface: lan0
or
server:
interface: lo
and so on, unbound-checkconf will crash.
This fix should be added to Jammy so configuration files and network interfaces can be properly validated for unbound.
The bug was fixed by adding a few commits from upstream as patches to unbound-checkconf. A function in unbound-checkconf.c was modified to resolve the interface name and check
that it works correctly. Meanwhile a commit that modifies the function resolve_interface_names in listen_dnsport.c and its calls was added as a patch to allow interface resolution to work correctly.
[Test Plan]
The following test can be used to reproduce the error:
# lxc launch images:ubuntu/jammy test-unbound
# lxc exec test-unbound bash
# apt update && apt dist-upgrade -y
# apt install unbound -y
# echo "
server:
interface: lo" >> /etc/unbound/unbound.conf
# unbound-checkconf
[Where problems could occur]
Since the resolve_interface_names function had to be updated for the unbound-checkconf to work, the places where it is called in the unbound package also had to be modified. This could lead to changes in behavior within unbound-control and the unbound daemon when checking interface names. Although this function will match the behavior upstream and in Kinetic, commits related to the handling of this function may be missed by the patch files.
[Other Info]
The issue was fixed upstream and was fixed in Kinetic through the most recent merge into Ubuntu.
[Original Description]
in unbound config one of the valid ways to specify IPs to listen on is to specify an interface name. e.g.
```
server:
interface: lan0
```
unbound starts and works correctly, but unbound-checkconf returns an error:
```
# unbound-checkconf
[1661781808] unbound-checkconf[4362:0] fatal error: cannot parse interface specified as 'lan0'
```
this bug was fixed upstream https://github.com/NLnetLabs/unbound/issues/574 but it's still present in ubuntu 22.04 |
[Impact]
When a user attempts to run unbound-checkconf and any of their stated interfaces matches the name of an existing network interface, the program will crash and will be unable to verify the configuration.
For example, if an unbound configuration file contains something like
server:
interface: lan0
or
server:
interface: lo
and so on, unbound-checkconf will crash.
This fix should be added to Jammy so configuration files and network interfaces can be properly validated for unbound.
The bug was fixed by adding a few commits from upstream as patches to unbound-checkconf. A function in unbound-checkconf.c was modified to resolve the interface name and check
that it works correctly. Meanwhile a commit that modifies the function resolve_interface_names in listen_dnsport.c and its calls was added as a patch to allow interface resolution to work correctly.
[Test Plan]
The following test can be used to reproduce the error:
# lxc launch images:ubuntu/jammy test-unbound
# lxc exec test-unbound bash
# apt update && apt dist-upgrade -y
# apt install unbound -y
# echo "
server:
interface: lo" >> /etc/unbound/unbound.conf
# unbound-checkconf
[Where problems could occur]
Since the resolve_interface_names function had to be updated for the unbound-checkconf to work, the places where it is called in the unbound package also had to be modified. This could lead to changes in behavior within unbound-control and the unbound daemon when checking interface names. Although this function will match the behavior upstream and in Kinetic, commits related to the handling of this function may be missed by the patch files.
The new patches also contain new memory allocation statements, so memory leaking from unfreed callocs can also be an issue.
[Other Info]
The issue was fixed upstream and was fixed in Kinetic through the most recent merge into Ubuntu.
[Original Description]
in unbound config one of the valid ways to specify IPs to listen on is to specify an interface name. e.g.
```
server:
interface: lan0
```
unbound starts and works correctly, but unbound-checkconf returns an error:
```
# unbound-checkconf
[1661781808] unbound-checkconf[4362:0] fatal error: cannot parse interface specified as 'lan0'
```
this bug was fixed upstream https://github.com/NLnetLabs/unbound/issues/574 but it's still present in ubuntu 22.04 |
|
| 2022-09-16 18:37:01 |
Bryce Harrington |
unbound (Ubuntu Jammy): status |
In Progress |
Fix Committed |
|
| 2022-09-21 15:16:23 |
Andreas Hasenack |
unbound (Ubuntu Jammy): status |
Fix Committed |
In Progress |
|
| 2022-10-17 12:46:08 |
Timo Aaltonen |
unbound (Ubuntu Jammy): status |
In Progress |
Fix Committed |
|
| 2022-10-17 12:46:10 |
Timo Aaltonen |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2022-10-17 12:46:13 |
Timo Aaltonen |
bug |
|
|
added subscriber SRU Verification |
| 2022-10-17 12:46:16 |
Timo Aaltonen |
tags |
server-todo |
server-todo verification-needed verification-needed-jammy |
|
| 2022-10-19 22:08:39 |
Lena Voytek |
tags |
server-todo verification-needed verification-needed-jammy |
server-todo verification-done-jammy verification-needed |
|
| 2022-10-21 14:47:16 |
Lena Voytek |
tags |
server-todo verification-done-jammy verification-needed |
server-todo verification-done verification-done-jammy |
|
| 2022-10-25 08:19:25 |
Launchpad Janitor |
unbound (Ubuntu Jammy): status |
Fix Committed |
Fix Released |
|
| 2022-10-25 08:19:30 |
Łukasz Zemczak |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
