- Sat Nov 28, 2020 7:34 am
#89603
Hello,
There is something unclear from which I will be happy to learn by the expert here.
Today, most of our connection from ESP8266 to the cloud is secure and based TLS connection.
This require to get server and validate it certificate and chain of trust.
We used a library SecureWifiClient that wrap for us all the required action.
I know that one of the steps to validate a certificate the web browser need to validate that the date is ok. Which means ithe certification is not too old nor too "new" (certificarion expire check).
I wonder how can an ESP can validate it because it dows not have system clock and date like operation system has.
Is anyone here can explian ?
Thanks
There is something unclear from which I will be happy to learn by the expert here.
Today, most of our connection from ESP8266 to the cloud is secure and based TLS connection.
This require to get server and validate it certificate and chain of trust.
We used a library SecureWifiClient that wrap for us all the required action.
I know that one of the steps to validate a certificate the web browser need to validate that the date is ok. Which means ithe certification is not too old nor too "new" (certificarion expire check).
I wonder how can an ESP can validate it because it dows not have system clock and date like operation system has.
Is anyone here can explian ?
Thanks
