使用 TLS 加密并验证证书
保护传输中的数据，并验证服务器可信
使用 TLS 加密并验证证书 是 CoddyKit 上的免费 Arduino & IoT Academy 课时。 这是第 3 节课，共 4 节。 你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。 这是 Arduino & IoT Academy 学习路径的一部分，你的进度在网页和 CoddyKit 应用中同步。 Arduino & IoT Academy 课程共包含 4 节课。
本课时的部分内容尚未翻译，以英文显示。
Why Encrypt at All
Data crossing WiFi and the internet passes many hands. Encryption scrambles it so only the intended server can read your readings. 🔒
Meet TLS
TLS is the layer that turns HTTP into HTTPS. It encrypts the channel between your device and a server so eavesdroppers see only noise.
The Handshake
Before any data flows, the two sides agree on keys in a handshake. This setup proves the server's identity and locks in a shared secret.
What a Certificate Proves
A server presents a certificate signed by a trusted authority. It proves the server really is who it claims to be, not an imposter.
Encryption Without Verification
Encrypting but skipping checks is dangerous. Without verification, an attacker can sit in the middle, hold the keys, and read everything.
The Man in the Middle
A man-in-the-middle impersonates the server and relays your traffic. Verifying the certificate is exactly what stops this attack cold.
Use WiFiClientSecure
On the ESP32, WiFiClientSecure handles TLS connections. It is the secure cousin of the plain client you used for HTTP.
#include <WiFiClientSecure.h>
WiFiClientSecure client;Pin the Root CA
Give your device the server's root certificate so it can verify trust. This pinned CA is how the board knows the server is genuine.
client.setCACert(root_ca); // verify the server against this trusted CANever Skip the Check
Calling setInsecure turns off all verification. setInsecure is fine for a quick test but should never reach a shipped product.
client.setInsecure(); // DANGER: trusts any server, use only for testingCertificates Expire
Every certificate has an expiry date, so verification needs the right time. A device with the wrong clock may wrongly reject a valid server.
Encrypt MQTT Too
TLS is not just for HTTPS. Point your MQTT client at a TLS broker port like 8883 to protect your pub/sub messages the same way.
Quick Check
Encryption alone is not enough. What else matters?
Recap
TLS encrypts traffic and certificates prove identity. Use WiFiClientSecure, pin a trusted CA, keep the clock right, and never ship setInsecure. 🛡️
常见问题解答
「使用 TLS 加密并验证证书」课时是免费的吗？
是的 — 「使用 TLS 加密并验证证书」的完整文本可在网页上免费阅读。要进行交互式练习（内置代码编辑器和全天候 AI 导师）并解锁 Arduino & IoT Academy 课程的其余内容，请升级到 CoddyKit PRO。 Arduino & IoT Academy 课程共包含 4 节课。
「使用 TLS 加密并验证证书」这节课中我会学到什么？
保护传输中的数据，并验证服务器可信 你通过在浏览器中直接运行的动手代码来练习 Arduino & IoT Academy，全天候 AI 导师会在你学习这节课的过程中回答你的问题。
学习 Arduino & IoT Academy 需要有经验吗？
无需任何先前经验。CoddyKit 上的 Arduino & IoT Academy 课程适合初学者到高级学习者，你可以从这里开始或从头开始，按照自己的节奏学习。 这是第 3 节课，共 4 节。
「使用 TLS 加密并验证证书」课时需要多长时间？
大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动，所以你能稳步进步，并在网页和应用中从离开的地方继续。
我能在这节 Arduino & IoT Academy 课中编写并运行代码吗？
能。每节 Arduino & IoT Academy 课都包含内置代码编辑器，你可以在浏览器中直接编写并运行真实代码，并获得即时 AI 反馈 — 无需本地设置。