- Sun Dec 22, 2019 6:29 am
#84996
Assume ESP8266 as an SSL Client, and has to connected to two different SSL Server. And then How?
Moderator: eriksl
- Sun Dec 22, 2019 6:43 am
#84997
Remove the SSL code and use a reverse proxy that does the encapsulation.
SSL is not something, due to it's concept/design/size, you should be running on a microcontroller anyway.
SSL is not something, due to it's concept/design/size, you should be running on a microcontroller anyway.
- Sun Dec 22, 2019 7:05 am
#84998
Do them one at a time and swap between them.
What are you connecting to? And what is the protocol?
esp8266_abc wrote:Assume ESP8266 as an SSL Client, and has to connected to two different SSL Server. And then How?
Do them one at a time and swap between them.
What are you connecting to? And what is the protocol?
- Sun Dec 22, 2019 7:07 am
#84999
I disagree - sometimes you don't have a choice. I'm running devices connected to the public Internet and I need to make sure my connections are secure both from a data perspective and a command perspective. I am using SSL and it's working fine, but you need to work within your micro's limits.
eriksl wrote:Remove the SSL code and use a reverse proxy that does the encapsulation.
SSL is not something, due to it's concept/design/size, you should be running on a microcontroller anyway.
I disagree - sometimes you don't have a choice. I'm running devices connected to the public Internet and I need to make sure my connections are secure both from a data perspective and a command perspective. I am using SSL and it's working fine, but you need to work within your micro's limits.
