There are some libraries I return to time and time again in my projects—libraries that make complex security straightforward to implement. WolfSSL is one of those. With native support for the Pico and Pico 2, plus excellent documentation, it’s become an essential tool in my workflow.
I first used WolfSSL on my initial Pico IoT project, where I needed TLS to secure MQTT communications. Before finding WolfSSL, I spent weeks pulling my hair out trying to get other libraries working, battling poor documentation, inconsistent examples, and frustration. Then I discovered WolfSSL’s TLS library, and the experience was completely different. Everything was clearly documented, and there were real examples to follow. While I had to do some porting since full support for the Pico W and Pico 2 W wasn’t available at the time, even that process was painless.
Since then, I’ve relied on WolfSSL in multiple IoT projects, whether for Web Services or WebSocket implementations. Over time, the library has only gotten better, now offering full native support for the Pico W and Pico 2 W.
But WolfSSL is more than just a TLS library—it’s an entire ecosystem of security-focused tools. The WolfCrypt library provides essential cryptographic primitives, which I’ve used to protect credentials with hashing algorithms. Secure Boot capabilities allow us to build trust into the firmware running on a Pico or Pico 2.
For even deeper security, Trusted Platform Module (TPM 2.0) integration with WolfSSL could add another layer of protection, enabling full trust in firmware and secure update processes.
WolfSSL libraries are all released under GPLv3, making them accessible for open-source projects with strong community support, while also offering commercial licensing for closed-source implementations.
Simply put, WolfSSL is one of my library heroes.
