-
Notifications
You must be signed in to change notification settings - Fork 3.8k
[24.10] kea: bump to 2.6.4 #27944
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[24.10] kea: bump to 2.6.4 #27944
Conversation
64b22d7 to
9a5d644
Compare
9a5d644 to
82797a6
Compare
pprindeville
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
|
Not sure why it's getting build failures... |
|
Converted this back to draft as
It looks like it's actually failing when trying to build the package index, not the package itself: I am able to successfully build the package and am using it successfully now. |
Create kea state directories with mode 0750 per restrictions added in 2.6.3 Refresh patches Fixes the following CVEs: * CVE-2025-32803: Change the umask to no group write and no other access at the entry of Kea server/agent binaries * CVE-2025-32801: kea-dhcp4, kea-dhcp6, kea-dhcp-ddns, and kea-ctrl-agent will now only load hook libraries from the default installation directory Full upstream changelogs are available at: https://downloads.isc.org/isc/kea/2.6.1/Kea-2.6.1-ReleaseNotes.txt https://downloads.isc.org/isc/kea/2.6.2/Kea-2.6.2-ReleaseNotes.txt https://downloads.isc.org/isc/kea/2.6.3/Kea-2.6.3-ReleaseNotes.txt https://downloads.isc.org/isc/kea/2.6.4/Kea-2.6.4-ReleaseNotes.txt Signed-off-by: Noah Meyerhans <[email protected]>
82797a6 to
d7c3416
Compare
|
Merging this change. CI issues are tracked with openwrt/gh-action-sdk#57. |
📦 Package Details
Maintainer: @nmeyerhans, @pprindeville
Description:
Bump kea to the latest release on the 2.6.y branch on the openwrt-24.10 branch
🧪 Run Testing Details
✅ Formalities
If your PR contains a patch:
git am(e.g., subject line, commit description, etc.)
We must try to upstream patches to reduce maintenance burden.