Report information
The Basics
Id:
47168
Status:
review
Priority:
Low/Low
Queue:

People
BugTracker
Version Fixed:
(no value)
Version Found:
4.4.0
Versions Affected:
(no value)
Versions Planned:
4.4.2 4.1-ESV-R16
Priority:
P2 Normal
Severity:
S2 Normal
CVSS Score:
(no value)
CVE ID:
(no value)
Component:
(no value)
Area:
feature

Dates
Created:Tue, 13 Feb 2018 09:25:07 -0500
Updated:Mon, 21 Jan 2019 12:26:59 -0500
Closed:Not set



This bug tracker is no longer active.

Please go to our Gitlab to submit issues (both feature requests and bug reports) for active projects maintained by Internet Systems Consortium (ISC).

Due to security and confidentiality requirements, full access is limited to the primary maintainers.

Date: Tue, 13 Feb 2018 14:25:07 +0000
To: bind9-public@isc.org
From: cathya@isc.org
Subject: ompapip/connection.c accepts only an HMAC_MD5 key
We can successfully create an omapi key with dhcp 4.4.0, but we can't use it to connect to dhcp. There is code in ompapip/connection.c that accepts only an HMAC_MD5 key. Please see details in the attached msg file. One of our developers has proposed a patch (also attached). Could you please review and consider including in an upcoming dhcpd release?
Subject: omapi_hmac.patch

Message body not shown because it is not plain text.

Reviewed the patch: OK. Created the rt47168 branch and applied the patch to it. Now I put the ticket in the review queue even it was already reviewed because I have no better solution...
On Tue Mar 06 14:45:03 2018, tmark wrote: > Did you conduct any form of tests with this? => no, this is why I asked if we already have a system test using omapi. So it seems the ticket has to stay in the review queue until someone tests it...