Skip to content
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

Update to LTS_07_2021_Ref01 (CA-167) #122

Open
MartinTJDK opened this issue Nov 18, 2021 · 11 comments
Open

Update to LTS_07_2021_Ref01 (CA-167) #122

MartinTJDK opened this issue Nov 18, 2021 · 11 comments

Comments

@MartinTJDK
Copy link
Contributor

Any plans for update to LTS_07_2021_Ref01?

@github-actions github-actions bot changed the title Update to LTS_07_2021_Ref01 Update to LTS_07_2021_Ref01 (CA-167) Nov 18, 2021
@MartinTJDK
Copy link
Contributor Author

@mahavirj Do you know, if it is prioritised?

@lhespress
Copy link
Collaborator

@MartinTJDK There isn't plan for update to LTS_07_2021_Ref01? What new functions for your project need update it?

@MartinTJDK
Copy link
Contributor Author

@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.

@epictrave
Copy link

@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)

@MartinTJDK
Copy link
Contributor Author

@epictrave I agree. The certificate bundle has to be updated. But it would also be nice to get bugfixes as well.

@MartinTJDK
Copy link
Contributor Author

@mahavirj @lhespress Is it something you will consider?

@lhespress
Copy link
Collaborator

@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.

@matgardon
Copy link

@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).

@lhespress
Copy link
Collaborator

lhespress commented Feb 17, 2022

@matgardon We have create a merge request for update it to LTS_01_2022_Ref01 and will release it after review finish.

@matgardon
Copy link

@lhespress awesome news, thanks for the follow up 🙏

@shahpiyushv
Copy link
Collaborator

This has now been pushed out to the repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants