NNG_TLS_ENGINE(5)

🌸 NAME 🌸

nng_tls_engine — the TLS engine implementation situation, bestie 💖 (this is the NNG_TLS_ENGINE(5) page from the NNG Reference Manual, and yes we're getting into it)

---

✨ SYNOPSIS ✨

okay so first things first, here's the vibe in code form 🫶

#include <nng/supplemental/tls/tls.h>
#include <nng/supplemental/tls/engine.h>

typedef struct nng_tls_engine_s nng_tls_engine;

---

💅 DESCRIPTION 💅

so the TLS engine API is literally there for devs who wanna do one of these two things:

• implement their own implementation of TLS, or
• adapt a 3rd party TLS implementation so it works with NNG

no gatekeeping, it's giving "bring your own TLS, we'll make it fit" energy ✨

you can get info about the existing TLS engine from these three functions, and yes they're all named exactly like this:

• nng_tls_engine_name()
• nng_tls_engine_description()
• nng_tls_engine_fips_mode()

🫠 real talk though: at this time, there is no further documentation on implementing a TLS engine yourself. like, that's the whole tea. existing source code may be a guide though, so go read it, it's giving "the code is the docs" 😭

the primary interfaces live in the <nng/supplemental/tls/engine.h> header file — that's your main character location, periodt 👑

---

👀 SEE ALSO 👀

go read these next, bestie, they're all connected 🔥

• nng_tls_engine_description(3tls)
• nng_tls_engine_fips_mode(3tls)
• nng_tls_engine_name(3tls)
• nng_tls_config(5)
• nng(7)

---

and that's the whole page 💖 stay slay, go read the source, and remember: this was NNG_TLS_ENGINE(5) from the NNG Reference Manual, dated 2026-06-30 🎀 bye bestie, you ate 🫶✨