# Stork 0.20.0, September 8th, 2021, Release Notes Welcome to Stork 0.20.0, another monthly development release. The changes introduced in this version are: * **Agent re-registration fix**. In earlier Stork versions, a previously authenticated agent was sometimes not recognized by the server upon restart, which forced a new registration and required the administrator to re-authenticate the machine. This problem has been fixed. [#528,#558]. On a related note, the nginx example configuration has been tweaked so the agent download script now works better. [#557] * **Clear text passwords handling**. The `view configuration` feature previously showed the whole Kea configuration, including sensitive information such as passwords. Now the full configuration is shown only when viewed by a user with super-admin credentials. Admins are still able to see the configuration, but all passwords are obscured. [#561] * **Certificate import**. By default, the Stork server generates all its certificates and keys on its own; however, some operators don't like self-signed certificates. The ability to import externally generated certificates has been added. The `stork-tool` now has a `cert-import` command; the long-term goal is to provide the ability to use properly signed certificates by deployments that have their own proper certificate authorities. This feature is experimental. Please do share your feedback. [#570] * **Stork Agent and `include` statements in Kea control agent configuration**. The Kea control agent (CA) has the ability to `include` files in its configuration, which confused earlier Stork agents. That problem has been fixed [#564]. * **PostgreSQL 10 and minimum version check**. Earlier Stork versions required PostgreSQL 11 to run properly. If an old PostgreSQL version was used, Stork ran but some operations failed, sometimes with cryptic error messages, e.g. "cannot cast type jsonb to integer." Backward compatibility has been improved and now Stork should work with PostgreSQL 10, but it has not been well-tested. The Stork server prints a warning if the version detected is too old (older than 10), but still attempts to run [#571]. * **Build and test improvements**. The unit tests no longer ask for passwords, if the default test password works [#555]; and the build procedure has been improved, so it behaves better with Docker running on MacOS [#490]. Please see this link for known issues: https://gitlab.isc.org/isc-projects/stork/-/wikis/Known-issues. ## Incompatible Changes * None. ## Release Model Stork has monthly development releases, with some exceptions. We encourage users to test the development releases and report back their findings on the stork-users mailing list, available at https://lists.isc.org/mailman/listinfo/stork-users. 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. It is available on ReadTheDocs.io at https://stork.readthedocs.io/en/latest/, and in source form in the docs/ directory. 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 will become available once it reaches the 1.0 milestone. Existing ISC customers that consider themselves early adopters may get involved in the development process, including roadmap, features planning, and early testing, but the software maturity level does not constitute a typical professional service before the 1.0 milestone. 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 Stork 0.18.0 release. ``` * 158 [build] marcin Corrected issues with the nginx-server.conf, an example Nginx configuration file providing the reverse proxy setup for Stork. The proxy now correctly forwards calls to download the Stork Agent installation script. The updated configuration also allows for accurately determining the Stork server URL while generating the downloaded script. (Gitlab #557) * 157 [func] godfryd, slawek Added cert-import command to stork-tool. This allows importing CA key and cert, and server key and cert. (Gitlab #570) * 156 [build] marcin Running unit tests no longer requires specifying a password explicitly. Renamed database connection specific environment variables in the stork-tool. (Gitlab #555) * 155 [func] slawek Added resolving the include statement in Kea configuration when an agent is detecting applications. (Gitlab #564) * 154 [bug] slawek Prevent agent re-registration after its restart. (Gitlab #528 and #558) * 153 [bug] slawek Corrected an issue with fetching Stork events from the databases running on PostgreSQL 10. Also, the Stork server requires PostgreSQL version 10 or later. (Gitlab #571) * 152 [build] marcin Resolved an issue with building Stork packages in Docker on the MacOS. (Gitlab #490) * 151 [func] slawek Obfuscate sensitive Kea configuration parts displayed using JSON viewer. (Gitlab #561) ``` Thank you again to everyone who assisted us in making this release possible. We look forward to receiving your feedback.