We had encounter a big problem with the TLS1.2 in SDK3.5.2 and Microsoft Azure. I saw several posts related to this problem and at current time, the unique solution is to use TLS1.1. I would like to know if an update of the lib BESL is planned to fix the problem. In a earlier post, I try to correct the problem by adding the SNI by extension (because I believe that problem is due of the lack of the SNI in the client hello message in the TLS handshake) (HTTPS with SNI extension) but in the same way, I fall on a bug.
Thank you for your answers,
I would like to know if an update of the lib BESL is planned to fix the problem.
SNI will be supported, the question is *when* will the fix be available.