HotLoop core 4.21.0 release notes
This release adds X.509 sign-in to the OPC UA server, takes the 64 byte password cap off it, and turns the deprecated security policies off by default. It also widens the CODESYS alarm import. Built on 4.20.2.
What changed
Section titled “What changed”- A client can sign in to the OPC UA server with an X.509 certificate. An admin attaches the client’s public certificate to a HotLoop user (Settings, OPC UA certificates, or the API, or the MCP tools), and a client that holds the private key signs in as that user with that user’s permissions. Revoking a certificate ends its live session within ten seconds, and every certificate sign-in and every refusal is in the logbook. It is off until
HOTLOOP_OPCUA_SERVER_ALLOW_X509=true(chartopcuaServer.allowX509). The device driver can sign in the same way withuserCertificateanduserPrivateKey(RSA, the key sealed like a password). A trusted CA with a name rule is not built. - Passwords of 65 to 72 bytes now sign in over OPC UA. They always worked in the web UI. The library the server is built on refused any user name token whose password was over 64 bytes.
- The deprecated security policies
Basic128Rsa15andBasic256are off by default. The server no longer lists them and a client that asks for one by name is refused when the channel opens. This applies to new installs and to upgrades. A legacy client that speaks nothing newer connects again withHOTLOOP_OPCUA_SERVER_ALLOW_DEPRECATED_POLICIES=true(chartopcuaServer.allowDeprecatedPolicies: true), and the server says so at start. The option to turn them off is open upstream too (pull request 66). - The CODESYS alarm import reads an Outside range alarm. The IDE’s Export Alarms writes
OutOfAreafor it, and it comes across as two alarms, aloat the lower limit and ahiat the upper one. Inside the range, Change, Event and Alarm (API) are listed as skipped with the reason: nothing here says them honestly. The importer was widened from an export of every observation type the IDE offers, kept as a test fixture.
API changes
Section titled “API changes”- New:
GET /api/opcua/certificates,GETandPOST /api/users/{username}/certificates,POST /api/users/{username}/certificates/{thumbprint}/revoke,DELETE /api/users/{username}/certificates/{thumbprint}, allusers.manage. Five new MCP tools, 133 in all. - One migration, 0027: the
user_certificatestable (public certificates only). It is in the backup.
Upgrading
Section titled “Upgrading”A plain helm upgrade, or the Quadlet auto-update. Check first whether any OPC UA client of yours is on Basic256 or Basic128Rsa15 (Ignition’s connection shows it): that client stops connecting after the upgrade until you either move it to Basic256Sha256 or set the legacy switch above. A rollback to the previous release was not tried with the new table in place.
-
All four charts (
hotloop,hotloop-iot,hotloop-edge,hotloop-edge-relay) are at 4.21.0, with every earlier version still in the index. -
This build is amd64 only, and
stablekeeps the arm images it holds. The next release is one small version bump that builds the arm images.