Hello everyone!
I mentioned it at the beginning of the week with the release of Gladys Assistant v4.8.2, I made a fairly significant fix on Gladys Plus. I’m sharing the message I sent by email to all Gladys Plus contributors:
Gladys Plus Update
In Gladys Plus, you know that all traffic is end-to-end encrypted.
I realized that when encrypted requests were too large, the encryption failed because the encoding function was not designed to support large messages.
To fix this bug, I had to change the encoding mechanism, but as you can imagine, this mechanism is not backward compatible.
To ensure service continuity, I have therefore scheduled a two-step update:
-
A first update went out at the beginning of the week, Gladys Assistant 4.8.2. This update brings this new encoding function, but does not activate it. The goal is for your instances to be ready to encrypt/decrypt these « next-generation » messages in due time.
-
A second update will go out tomorrow, and will « activate » this new function: your instances will start encrypting requests with the new encoding function and decrypting requests coming from the interface.
How to update?
If you installed Gladys with the official Raspberry Pi OS image, your instances will update automatically in the coming hours. This can take up to 24 hours, no need to worry.
If you installed Gladys with Docker, check that you are using Watchtower (See the documentation)