Skip to content

Releases: Tinkerforge/esp32-remote-access

v.1.2.43

15 Sep 06:29
Compare
Choose a tag to compare
  • fix users not beeing able to change email-address when a wem2 is configured

v1.2.42

11 Sep 06:57
Compare
Choose a tag to compare
  • fix webinterface not reloading after firmware update of a device
  • fix spamming errors when frontend is unable to connect to server

v1.2.41

10 Sep 07:19
Compare
Choose a tag to compare
  • fixed small visual bugs in the device list
  • request persistent storage to combat rarely occurences of browsers deleting the cache leading to users getting logged out
  • updated dependencies

v1.2.40

19 Aug 08:41
Compare
Choose a tag to compare
  • change custom built Docker containers to run with non root user

v1.2.39

18 Aug 13:41
Compare
Choose a tag to compare
  • increased max bodysize. This is needed for the charge_log via email feature
  • eliminate configurations that were not using env variables. This ensures better deployment automatization

v1.2.38

13 Aug 12:53
Compare
Choose a tag to compare
  • fix not beeing able to access static pages when webinterface was loaded from the server cache
  • add button to resend verification token

v1.2.37

13 Aug 07:22
Compare
Choose a tag to compare
  • fix requests to static assets on the devices

v1.2.36

12 Aug 12:41
Compare
Choose a tag to compare
  • fix users getting logged out from the app
  • fix remote access not working when local login is enabled and the webinterface is not in the server-cache
  • added some recomendations to error messages

v1.2.35

06 Aug 12:43
Compare
Choose a tag to compare
  • add versioning of website content. This allows to promt the user to reload in case changes were made
  • cache the webinterfaces on the server. This reduces the loading times
  • add server component for sending charge-logs via e-mail

v1.2.34

31 Jul 08:09
Compare
Choose a tag to compare
  • fix an issue where a potentially malicious custom device firmware could steal the users encryption Key. It is highly unlikely that this happened and even in case it happened the attacker still needs to steal a session of the attacked user to be able to even get the encrypted data.