@@ -110,6 +110,31 @@ https://github.com/networkupstools/nut/milestone/13
110110 allows to pass the `certfile` argument needed for OpenSSL builds. [#3331]
111111 * The `libupsclient` (C) and `libnutclient` (C++) API were updated to
112112 report the ability to check `CERTIDENT` information. [#3331]
113+ * Introduced support for "authconf" files to store and convey NUT client
114+ authentication details. [issue #3329]
115+
116+ - `upsc`, `upscmd`, `upsrw` command-line client updates:
117+ * Enabled support for `nutauth.conf` files to provide credentials and/or
118+ SSL settings in the client which previously only did best-effort attempts
119+ at secure communications without an individual certificate, and only
120+ anonymously for reading. The new `-A filename` option defaults to trying
121+ to use a `nutauth.conf` file (if found in one of the default locations)
122+ but not failing if one is not usable; specific values can require use of
123+ such a file (`default`) or to not even try reading one (`none`).
124+ [issues #3329, #3411]
125+
126+ - `upslog` client/tool updates:
127+ * Added support for best-effort use of `nutauth.conf` files from default
128+ locations or via `-A` option, as described above. Since this client
129+ can establish multiple connections, keep in mind that currently it
130+ can only identify itself with some one (first seen) client certificate,
131+ if `CERTIDENT` settings are used. Multiple `CERTHOST` directives for
132+ specially trusted servers can be used. [#3329]
133+
134+ - `upsstats`, `upsset`, `upsimage` CGI client updates:
135+ * Added support for best-effort use of `nutauth.conf` files from default
136+ locations described above (no way to choose the location, other than
137+ by web-server environment variables for CGI calls). [#3329]
113138
114139 - `upsmon` client updates:
115140 * Introduced support for `CERTFILE` option, so the client can identify
@@ -134,6 +159,9 @@ https://github.com/networkupstools/nut/milestone/13
134159 much later (tell the sysadmin to increase `ulimit` or set up a more
135160 conservative `MAXCONN`). If there is a separate soft and hard limit,
136161 and `MAXCONN` exceeds the soft limit, try to raise the bar. [issue #3365]
162+ * If SSL configuration was provided, but the server failed to apply some
163+ aspect of that, it should now abort with an explanation (and not proceed
164+ with insecure start-up like it could do before). [issue #3331, PR #3435]
137165
138166 - Recipes, CI and helper script updates not classified above:
139167 * Introduced `ci_build.sh` settings and respective CI workflow settings
0 commit comments