Jump to content
Sign in to follow this  
stepanb

sslConnect dosn't work with some servers

Recommended Posts

Hi,

I tried to use sslConnect to communicate with Azure Event Hub. Host for endpoint is stepanb-eh.servicebus.windows.net and I can't connect. If I use same code with another server for example www.google.com I can connect. Only difference I see is length of URL. Any hints? 

Hardware: CC3200 Lanchpad with latest firmware

 

 

Stepan

Share this post


Link to post
Share on other sites

Does the Azure Event Hub validate the client-side certificate?  That could be a problem since Energia doesn't exactly expose an API for users to load their own client cert.  So the CC3200 uses whatever default client cert it comes with I think.

Share this post


Link to post
Share on other sites

Does the Azure Event Hub validate the client-side certificate?  That could be a problem since Energia doesn't exactly expose an API for users to load their own client cert.  So the CC3200 uses whatever default client cert it comes with I think.

Hi, there is no client-side certificate validation. I use it for example with ESP8266 and Arduino IDE and it works with no problem.

Share this post


Link to post
Share on other sites

Code is in ZIP archive http://1drv.ms/1ZTPs3t Correct response should be "Unauthorized" There is fake security key. Rest of code is real.

FYI- A bit late getting back to this, but I've confirmed on a Tiva-C TM4C123G LaunchPad with CC3100 that changing your client.connect(HOST, 443) to client.sslConnect(HOST, 443) results in connection failure.  Will have to dive deeper to see if I can find out anything regarding "why".

Share this post


Link to post
Share on other sites

FYI- A bit late getting back to this, but I've confirmed on a Tiva-C TM4C123G LaunchPad with CC3100 that changing your client.connect(HOST, 443) to client.sslConnect(HOST, 443) results in connection failure.  Will have to dive deeper to see if I can find out anything regarding "why".

Error from the SimpleLink WiFi is -208.

 

#define SL_ESEC_SOCKET_ERROR_E                (-208)  /* error state on socket    */

 

In contrast, www.ti.com:443 works fine (connects at least) with sslConnect().  Very odd!

Share this post


Link to post
Share on other sites

Did anyone ever get to the root of this?

@@stepanb I've tried your code as-is (just replaced my event hub details) and no luck :(

 

Could it possibly be the version, key size or CA of the certificate - causing the CC3200 SSL library problems?

 

SHA-256 with RSA Encryption ( 1.2.840.113549.1.1.11 )

 

[edit, adding link to my other post about this just to help me find it]

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this  

×
×
  • Create New...