packages/net/kea/Makefile, branch master

kea: update to 3.2.0

2026-06-30T01:52:48Z

Update to LTS version, which includes support for NAKing unknown class requests. https://gitlab.isc.org/isc-projects/kea/-/issues/4110 Signed-off-by: Philip Prindeville

kea: handle network reconfiguration without restarting

2026-06-01T15:25:37Z

Currently if a dynamic interface changes (VLAN, tunnel, etc) that Kea is listening on, it needs to be told externally to restart. The re-detect option avoids this. Signed-off-by: Philip Prindeville

kea: bump to 3.0.3

2026-06-01T11:11:10Z

3.0.3 is a security/vulnerability release on the stable 3.0 series. Notable fixes since 3.0.2: * **CVE-2026-3608** — A large number of bracket pairs in a JSON payload sent to any endpoint caused a stack overflow during recursive parsing. The exploit does not need a syntactically valid command, so it bypasses RBAC and the command filters on the High-Availability endpoints (upstream #4275 / #4288 / #4387). * Null dereference when configuring the Control Agent with a socket entry that lacks the mandatory ``socket-name`` is now caught (#4388, #4365). * UNIX command sockets are created group-writable so Stork 2.4.0+ and other tooling using the configured group can talk to the daemon (#4398, #4260). Upstream's release notes flag "no incompatible changes" and "no known issues" for this bump. All current patches still apply cleanly. Release notes: https://ftp.isc.org/isc/kea/3.0.3/Kea-3.0.3-ReleaseNotes.txt Signed-off-by: Alexandru Ardelean

kea: ship admin-utils.sh and kea-shell Python modules

2026-06-01T05:11:11Z

kea-admin and kea-shell were shipped without their helper script and Python modules respectively, leaving both non-functional. Ship the missing files, add +python3-light +python3-urllib +python3-openssl to kea-shell, and rewrite its meson-baked host-absolute shebang and sys.path.append to the on-target /usr/bin/python3 + $(PYTHON3_PKG_DIR). Signed-off-by: Alexandru Ardelean

kea: depend on the concrete log4cplus, not the -any virtual

2026-05-30T06:55:38Z

Commit 1ea43c352 ("kea: fix kea-libs dependencies") replaced the direct +log4cplus dependency on kea-libs with the virtual name +log4cplus-any. With only one log4cplus implementation in the feed, nothing actually PROVIDES log4cplus-any other than the auto-generated "package name + -any" alias on log4cplus itself. apk treats `-any`-suffixed names as ambiguous virtuals that the admin must resolve explicitly, even when only one provider exists, and refuses to install: ERROR: unable to select packages: log4cplus-any (virtual): note: please select one of the 'provided by' packages explicitly provided by: log4cplus required by: kea-libs-3.0.2-r7[log4cplus-any] That bubbles up to every kea subpackage runtime test in CI (kea-admin, kea-ctrl, every kea-dhcp* and kea-hook-*) and fails the multi-arch test build with exit code 3. Switch back to +log4cplus directly; the +libstdcpp addition from that earlier commit stays — it was the genuinely useful part of the change. Bump PKG_RELEASE for the redo. Signed-off-by: Alexandru Ardelean

kea: fix kea-libs dependencies

2026-04-16T16:29:26Z

Include libstdc++ and log4cplus libraries. Signed-off-by: Philip A. Prindeville

kea: importer for legacy isc-dhcp-v4 UCI configs

2026-04-09T23:36:46Z

Now that ISC-DHCP is EOLs, users might want to transparently to the functionality of Kea. This supports most of the functionality of ISC-DHCP for v4. Signed-off-by: Philip Prindeville

kea: add support synthesizing imported config files

2026-04-09T23:36:46Z

Configuring Kea JSON files is not trivial, and this might impede the adoption of Kea as a DHCP server. There are, however, many users who used its predecessor ISC-DHCP, at least for DHCPv4. A filter could ingest the legacy UCI and synthesize a JSON config file for Kea DHCPv4. Signed-off-by: Philip Prindeville

net/kea: assign PKG_CPE_ID

2026-03-22T06:32:43Z

cpe:/a:isc:kea is the correct CPE ID for kea: https://nvd.nist.gov/products/cpe/search/results?keyword=cpe:2.3:a:isc:kea Signed-off-by: Fabrice Fontaine

kea: make building with Openssl deprecated APIs off

2026-02-09T17:09:39Z

Some of the X.509 API got retired in 3.0.0 so we should check against the backward compatibility not being enabled. Signed-off-by: Philip Prindeville