TLS_CLIENT(3)

πŸ“¦ version 4.4.0, in alpine 3.24, arch rolling

πŸ’… TLS_CLIENT(3) πŸ’…

okay bestie, welcome to TLS_CLIENT(3) from the Library Functions Manual β€” this is the page for setting up a TLS connection and it is lowkey iconic ✨


🌸 NAME 🌸

tls_client, tls_server, tls_configure, tls_reset, tls_free β€” configure a TLS connection 🫢


✨ SYNOPSIS ✨

library β€œlibtls” libssl libcrypto #include <tls.h>

struct tls *
tls_client(void);

struct tls *
tls_server(void);

int
tls_configure(struct tls *ctx, struct tls_config *config);

void
tls_free(struct tls *ctx);

void
tls_reset(struct tls *ctx);

πŸ¦‹ DESCRIPTION πŸ¦‹

So a TLS connection is represented as a struct tls object, and everyone calls it a β€œcontext” πŸ’– A fresh new context gets created by either the tls_client() or tls_server() functions. Use tls_client() in TLS client programs, and tls_server() in TLS server programs. Slay, but make it networking 🌈

Then you can configure that context with tls_configure(). And yes, the same tls_config object can be used to configure multiple contexts β€” reuse is the vibe ✨

After configuration, tls_connect(3) can be called on objects created with tls_client(), and tls_accept_socket(3) on objects created with tls_server(). iykyk πŸ‘‘

After use, a TLS context should be closed with tls_close(3), and then freed by calling tls_free(). Important little detail: if tls_free() is called with an argument of NULL, no action occurs. Literally nothing happens, no drama 🫢

A TLS context can be reset by calling tls_reset(), allowing for it to be reused. This is essentially equivalent to calling tls_free(), followed by a call to the same function that was used to originally allocate the TLS context. Reset and re-enter, main character energy πŸ’…


πŸ”₯ RETURN VALUES πŸ”₯

tls_client() and tls_server() return NULL on error or an out of memory condition 😭

tls_configure() returns 0 on success or -1 on error. That’s the whole vibe check πŸ”₯


🌈 SEE ALSO 🌈


⭐ HISTORY ⭐

These functions appeared in OpenBSD 5.6 and got their final names in OpenBSD 5.7. Glow-up timeline fr fr ✨


πŸ‘‘ AUTHORS πŸ‘‘

Joel Sing <jsing@openbsd.org> β€” icon behavior πŸ‘‘


xoxo, this page’s source/version is Debian, dated July 7, 2025 β€” bye bestie πŸ’–πŸ«Ά

πŸ“¦ where this page comes from