esp-azure
esp-azure copied to clipboard
espressif
Update to LTS_07_2021_Ref01 (CA-167)
@MartinTJDK There isn't plan for update to LTS_07_2021_Ref01? What new functions for your project need update it?
@lhespress LTS_07_2021_Ref01 has several bugfixes, which we need. When continiously removing network connectivity, the "esp-azure" in combination with ESP network driver locks up, and never gets online again. Even resolving of host names fails at that point. I have also seen 0-pointer issues, which should have been fixed in azure sdk. All mentioned issues are only seen, when network is not stable.
@mahavirj @MartinTJDK @lhespress I think this repo needs LTS_07_2021_Ref01. Because of upcoming TLS certificate changes (from the current Baltimore CyberTrust CA Root to the DigiCert Global G2 CA root)
@epictrave I agree. The certificate bundle has to be updated. But it would also be nice to get bugfixes as well.
@MartinTJDK As mentioned earlier, no updates are planned in the near future, we are discussing which to update because of there are both Azure-iot-SDK-C and Azure-SDK-for-c to access Azure-IoT.
@lhespress I'm not sure this has been stated clearly enough by @epictrave so I'll just stress it again here: without this LTS, the source code will not contain the right CA for ESP32 devices to be able to connect to azure anymore, as explained in this blog post.
So getting this update, if not for all the other stability fixes, doesn't seem like optional for people using this repo when building their binaries for ESP devices connecting to azure.
If it's not officially upgraded, we will have to upgrade ourselves one way or another, or devices will not be able to connect to azure anymore (and that will happen soon).
@matgardon We have create a merge request for update it to LTS_01_2022_Ref01 and will release it after review finish.
