NNG_TLS_CONFIG(5)

✨ NAME ✨

nng_tls_config — the TLS configuration object, aka the lil glow-up container for all your TLS settings 💅

---

🌸 SYNOPSIS 🌸

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

typedef struct nng_tls_config nng_tls_config;

---

🎀 DESCRIPTION 🎀

okay so bestie, an nng_tls_config is literally one single TLS configuration object, and you use it to configure both TLS servers and TLS clients. main character energy for both sides of the handshake fr fr 🫶

The config data holds all the juicy details, like:

• certificate chains used for validation of remote peers 🔍
• local key and certificate material 🔑
• server names 🌐
• and so forth ✨

and on top of all that, a configuration can be used either in client mode or in server mode — pick your vibe.

Configuration objects may be shared, and they are reference counted (iconic, honestly). BUT — and this is the part you cannot skip — once a configuration is used, it enters a read-only state that precludes further modifications to the configuration. it's giving "frozen in place, no take-backs" 🧊 no editing after that, periodt.

Messages are allocated using the nng_tls_config_alloc() function, and deallocated using the nng_tls_config_free() function. that's the whole lifecycle, babes 💖

---

👑 SEE ALSO 👑

• nng_tls_config_alloc(3tls)
• nng_tls_config_auth_mode(3tls)
• nng_tls_config_ca_chain(3tls)
• nng_tls_config_own_cert(3tls)
• nng_tls_config_free(3tls)
• nng_tls_config_hold(3tls)
• nng_tls_config_server_name(3tls)
• nng(7)

---

and that's the whole page bestie, tysm for reading 🥹💜 this one's straight out of the NNG Reference Manual, dated 2026-06-30, and the page itself is NNG_TLS_CONFIG(5) — go forth and configure responsibly, mwah 🎀✨