--- title: Release notes 2.4.1 --- # Stork 2.4.1 Release Notes, May 13, 2026 Welcome to Stork 2.4.1, a maintenance release for the 2.4 stable series. There are no new features. The following bug fixes introduced in this version are: 1. **Fixed panic in LDAP**: We fixed a bug that could cause the server to panic during user authentication via LDAP. The authentication could be rejected if the user's Distinguished Name differed from the value known to the Stork server [#2411, #2303]. 2. **Crash fix**: The Stork server could crash when the monitored daemon had no control sockets specified; this has been fixed [#2426, #2403]. 3. **Fix for disappearing parameters**: Stork no longer erases Kea configuration parameters it does not recognize when it updates a Kea configuration. This is important when the Stork version is behind the Kea version and new parameters are introduced to Kea [#2412, #2328]. 4. **Relaxed TLS requirements**: The strict requirement for TLS 1.3 has now been relaxed. We added the `--db-tls-1-2-enabled` flag (the `STORK_DATABASE_TLS_1_2_ENABLED` environment variable) to allow lowering the minimum TLS version for database connections from 1.3 to 1.2 [#2409, #2319]. 5. **DB migration fix**: We fixed a database migration failure for an application with no daemons [#2408, #2317]. 6. **BIND 9 detection fix**: We fixed an issue where Kea, BIND 9, and PowerDNS detection failed to parse the CLI flags when the path to the binary contained a directory with the same name as the binary (e.g., `/var/lib/named/sbin/named`) [#2410, #2374]. 7. **Kea DDNS daemon detection fix**: Stork now correctly detects and monitors the kea-dhcp-ddns process [#2446, #2433]. 8. **Updated dependencies**: Several external dependencies were updated [#2431, #2448]. Please see this link for known issues: https://gitlab.isc.org/isc-projects/stork/-/wikis/Known-issues. ## Incompatible Changes There are no backward-incompatible changes in this release. ## Release Model Stork has stable (even-numbered minor version, e.g. 2.4.1) and development (odd-numbered minor version, e.g. 2.3.2) releases; development releases are issued bi-monthly with some exceptions. New stable releases are expected roughly every six months. For ISC's detailed software support policy, see https://kb.isc.org/docs/aa-00896#stork. We recommend using stable versions in production if possible. We encourage users to test development releases and report back their findings on the stork-users mailing list (available at https://lists.isc.org/mailman/listinfo/stork-users) or open GitLab issues. ISC professional support customers may also report issues via our support portal. This text references issue numbers. For more details, visit the Stork GitLab page at https://gitlab.isc.org/isc-projects/stork/issues. ## License Stork is released under the Mozilla Public License, version 2.0. https://www.mozilla.org/en-US/MPL/2.0 ## Download The easiest way to install the software is to use native deb or RPM packages. They can be downloaded from: https://cloudsmith.io/~isc/repos/stork/ The Stork source and PGP signature for this release may be downloaded from: https://downloads.isc.org/isc/stork The signature was generated with the ISC code-signing key, which is available at: https://www.isc.org/pgpkey ISC provides documentation in the Stork Administrator Reference Manual (ARM). It is available on ReadTheDocs.io at https://stork.readthedocs.io/en/latest/, and in source form in [the doc/ directory](https://gitlab.isc.org/isc-projects/stork/-/tree/master/doc). We ask users of this software to please let us know how it worked for you and what operating system you tested on. Feel free to share your feedback on the stork-users mailing list (https://lists.isc.org/mailman/listinfo/stork-users). We would also like to hear whether the documentation is adequate and accurate. Please open tickets in the Stork GitLab project for bugs, documentation omissions and errors, and enhancement requests. We want to hear from you even if everything worked. ## Support Professional support for Stork is available from ISC. We encourage all professional users to consider this option; Stork and Kea maintenance is funded with support subscriptions. For more information on ISC's Kea and Stork software support, see https://www.isc.org/support/. Free best-effort support is provided by our user community via a mailing list. Information on all public email lists is available at https://www.isc.org/mailinglists/. If you have any comments or questions about working with Stork, please share them to the stork-users list (https://lists.isc.org/mailman/listinfo/stork-users). Bugs and feature requests may be submitted via GitLab at https://gitlab.isc.org/isc-projects/stork/issues. ## Changes The following summarizes changes and important upgrades since the previous Stork stable release versioned 2.4.0. * 623 [bug] marcin Fixed detection and monitoring of the kea-dhcp-ddns process. (Gitlab #2446) * 622 [bug] slawek, piotrek Fixed a bug that could cause the server to panic during user authentication via LDAP. Authentication could be rejected if the user's Distinguished Name differed from the value known to the Stork server. (Gitlab #2411) * 621 [build] marcin, slawek Updated dependencies including Go 1.25.10, and several JavaScript, Python, Ruby and Go packages. (Gitlab #2431, #2448) * 620 [bug] slawek Fixed the Stork server crash when the monitored daemon had no control sockets specified. (Gitlab #2426) * 619 [bug] marcin Stork no longer erases Kea configuration parameters it does not recognize when it updates Kea configuration. This is important when Stork version is behind Kea version, and new parameters were introduced to Kea. (Gitlab #2412) * 618 [func] slawek Added the --db-tls-1-2-enabled flag (STORK_DATABASE_TLS_1_2_ENABLED environment variable) to allow lowering the minimum TLS version for database connections from 1.3 to 1.2. (Gitlab #2409) * 617 [bug] slawek Fixed a database migration failure for the application with no daemons. (Gitlab #2408) * 616 [bug] slawek Fixed Kea, BIND 9, and PowerDNS detection failing to parse the CLI flags when the path to the binary contained a directory named same as the binary (e.g., /var/lib/named/sbin/named). (Gitlab #2410) Thank you again to everyone who assisted us in making this release possible. We look forward to receiving your feedback.