@@ -106,6 +106,31 @@ https://github.com/networkupstools/nut/milestone/13
106106 allows to pass the `certfile` argument needed for OpenSSL builds. [#3331]
107107 * The `libupsclient` (C) and `libnutclient` (C++) API were updated to
108108 report the ability to check `CERTIDENT` information. [#3331]
109+ * Introduced support for "authconf" files to store and convey NUT client
110+ authentication details. [issue #3329]
111+
112+ - `upsc`, `upscmd`, `upsrw` command-line client updates:
113+ * Enabled support for `nutauth.conf` files to provide credentials and/or
114+ SSL settings in the client which previously only did best-effort attempts
115+ at secure communications without an individual certificate, and only
116+ anonymously for reading. The new `-A filename` option defaults to trying
117+ to use a `nutauth.conf` file (if found in one of the default locations)
118+ but not failing if one is not usable; specific values can require use of
119+ such a file (`default`) or to not even try reading one (`none`).
120+ [issues #3329, #3411]
121+
122+ - `upslog` client/tool updates:
123+ * Added support for best-effort use of `nutauth.conf` files from default
124+ locations or via `-A` option, as described above. Since this client
125+ can establish multiple connections, keep in mind that currently it
126+ can only identify itself with some one (first seen) client certificate,
127+ if `CERTIDENT` settings are used. Multiple `CERTHOST` directives for
128+ specially trusted servers can be used. [#3329]
129+
130+ - `upsstats`, `upsset`, `upsimage` CGI client updates:
131+ * Added support for best-effort use of `nutauth.conf` files from default
132+ locations described above (no way to choose the location, other than
133+ by web-server environment variables for CGI calls). [#3329]
109134
110135 - `upsmon` client updates:
111136 * Introduced support for `CERTFILE` option, so the client can identify
0 commit comments