GitHub usage of EC based certificates breaks LCM v2.1.2

[HomeACcessoryKid]

IT DOES NOT BREAK, a misunderstanding from my side When updating the root certificate, I forgot to add an old root CA to the file Fixed 3 April 18:50 CEST

Starting 1 April, people that use LifeCycleManager report that the access to GitHub.com does not work anymore. Analyses shows that GitHub now uses new certificates, and for the first time they use Elliptic Curve (EC) based certificates. Because the clients always worked with RSA based certificates, they are now broken. Because the clients are embedded and the way they update themselves is through GitHub.com, they are now stuck. These embedded clients are often deployed in wall sockets and other hard to reach places.

The request to the GitHub team is to provide a grace period in which they use RSA certificates again so the clients can update themselves to support EC. A version that supports EC has been created already, so it confirms the issue can be solved like this. For the record, it is encouraged to use the same root CA as today, DigiCertGlobalRootCA

This same text is registered in GitHub.com/feedback

[HomeACcessoryKid]

IT DOES NOT BREAK, a misunderstanding from my side When updating the root certificate, I forgot to add an old root CA to the file Fixed 3 April 18:50 CEST