Choosing a cryptographic library for Rust means balancing more than memory safety. Production deployments require portability, compliance, stable APIs, and a library that can evolve with changing security standards.
This technical webinar examines the design of the wolfssl-wolfcrypt crate, including how it interfaces with wolfCrypt, supports FIPS 140-3 validated and post-quantum cryptography, and enables a consistent cryptographic implementation across embedded and Linux platforms.
This webinar covers
- Selecting cryptography for production Rust applications
- Understanding the crate architecture and safety model
- Integrating FIPS 140-3 validated and post-quantum cryptography
- Deploying a portable cryptographic implementation across embedded and Linux platforms
- Long-term maintenance and the wolfSSL Rust roadmap
Ask the Expert: Answers Key Questions
Our experts answer key questions about what attendees will learn
Why can’t I just validate OpenSSL?
Because applications, middleware, and the Linux kernel may each rely on different cryptographic implementations. A unified FIPS deployment requires every component to use the validated cryptographic module.
How do you get every Linux component onto one FIPS module?
OpenSSL, NSS, GnuTLS, libgcrypt, and Linux kernel cryptography can be redirected to wolfCrypt FIPS through providers, PKCS#11, shims, and the kernel module.
What does verification actually involve?
Verification includes generate the required FIPS configuration, run the module self-tests, and verify that system cryptographic operations are using the validated module.
Register now to evaluate a production-ready cryptographic architecture for Rust.
Date: July 15 | 9 AM PT
As always, our webinar will include Q&A throughout. If you have questions about any of the above, please contact us at facts@wolfssl.com or call us at +1 425 245 8247.
Download wolfSSL Now