-
-
Notifications
You must be signed in to change notification settings - Fork 485
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Configuring an encryptionKey does not immediately switch to encryption #1980
Comments
Please export your configuration into a file and verify that the encryption key is actually set, and that it doesn't begin or end with white space. (I don't think the latter should matter, but better safe than sorry.) |
Here's my redacted config file: |
That looks ok to me. This might be a stupid question, but have you tried restarting the app completely? Do you then still see the messages unencrypted when they're published? |
That did the trick. I previously reinstalled the app after clearing all data, but because the default state is unencrypted, the issue persisted. This seems like a critical bug to me, however. One expects that if an encryption key is set that the data is actually encrypted. Thanks. |
I agree and am marking this as a bug. |
For some reason, I can't get the app (Owntracks 2.5.3) to encrypt the payloads. Even if I include a secret key, inspecting the results with MQTT Explorer shows that it is being sent in cleartext. Another device seems to encrypt without issue, and there seems to be no difference in settings for the two phones.
The text was updated successfully, but these errors were encountered: