Report information
The Basics
Id:
46771
Status:
resolved
Estimated:
2 hours (120 minutes)
Worked:
1.67 hours (100 minutes)
Users:
tmark: 1.67 hours (100 minutes)
Priority:
Low/Low
Queue:

People
Requestors:
Cc:
AdminCc:

BugTracker
Version Fixed:
4.4.0
Version Found:
(no value)
Versions Affected:
(no value)
Versions Planned:
4.4.0
Priority:
(no value)
Severity:
(no value)
CVSS Score:
(no value)
CVE ID:
(no value)
Component:
(no value)
Area:
feature

Dates
Created:Mon, 04 Dec 2017 14:09:15 -0500
Updated:Mon, 11 Dec 2017 07:30:28 -0500
Closed:Mon, 11 Dec 2017 07:30:04 -0500



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.

From: mcnally@isc.org
Subject: Feature Request - Support alternate crypto algorithms for securing OMAPI channel
To: dhcp-suggest@isc.org
Date: Mon, 04 Dec 2017 19:09:15 +0000
A customer has requested that we support OMAPI using other cryptographic algorithms (besides HMAC-MD5) to encrypt communication between the OMAPI client and the ISC DHCP server.
On Thu Dec 07 20:52:24 2017, tmark wrote: > Given feed back from support, I elected to add a new statement: > > key-algorithm <algorithm> > > Ready for review. => in RELNOTES I suggest "as the dhcpd:" -> "as the dhcpd server:". The patch should be given to QA and/or requestor to check it works as expected but the code is OK and IMHO should be merged without waiting for feedback.