[Nut-upsdev] RFE: Update NUT protocol to prefer aliases ATTACH/DETACH instead of LOGIN/LOGOUT
Jim Klimov
jimklimov at gmail.com
Wed Sep 23 19:14:57 BST 2026
Cheers fellow NUT developers,
Several recent discussions touched on discrepancies between the factual
NUT networked protocol and the requirements of RFC 9271
<https://www.rfc-editor.org/info/rfc9271/#section-4.2.1> - in particular,
the different naming of certain commands and responses. Subsequently I've
posted an issue to track ideas and development around this - feel free to
chime in, especially with ideas about keeping the solution backwards
compatible for older NUT and third-party clients conformant to the protocol
definition of their day: https://github.com/networkupstools/nut/issues/3637
As a heads-up, another noted discrepancy is that RFC-compliant
communications may not be anonymous. And the RFC review had questions about
the use of plaintext protocol connections, so we assured them we have
in-dialog STARTTLS or add-on stunnel etc. ability to protect the
monitoring/management traffic... So eventually NUT would grow (initially
optional, later default that can be reverted) settings to reject any
unauthenticated traffic for queries and other commands - even for the likes
of upsc client or common monitoring frameworks. More details on that in
https://github.com/networkupstools/nut/issues/3411 - and since PR
https://github.com/networkupstools/nut/pull/3435 we can easily pass SSL
details and login credentials to clients using a common configuration file.
Further work done in PR https://github.com/networkupstools/nut/pull/3607
aimed to close the gap for clients with multiple connections like upsmon,
upslog and upsstats.cgi to be able to talk with SSL/TLS servers managed by
different CA realms (different SSL contexts in OpenSSL terms). Generally
speaking, the SSL/TLS support should be working and easily (*the best we
can manage) configurable across the board as most of the points in epic
https://github.com/networkupstools/nut/issues/3329 are already ticked.
Hope this helps,
Jim Klimov
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/nut-upsdev/attachments/20260923/af6763f2/attachment.htm>
More information about the Nut-upsdev
mailing list