GNUTLS_OCSP_STATUS_REQUEST_ENABLE_CLIENT(3)

📦
version 3.8.13 · 7 versions
, in alpine 3.22, alpine 3.23, alpine 3.24, arch rolling, fedora 43, fedora 44, ubuntu stonking

💖 NAME 💖

gnutls_ocsp_status_request_enable_client — bestie, this is an API function and it's about to make your client go "hey server, got any OCSP tea for me?" 🍓

It lives in the gnutls manual, and yes, the whole page title is basically a keyboard smash, iykyk. 💅

✨ SYNOPSIS ✨

#include <gnutls/gnutls.h>

int gnutls_ocsp_status_request_enable_client(gnutls_session_t session,
gnutls_datum_t * responder_id, size_t responder_id_size, gnutls_datum_t
* extensions);

That's a lot of words for one function, but we move. 🌈

🎀 ARGUMENTS 🎀

  • gnutls_session_t session — it's a gnutls_session_t type, your lil session baddie. The main character here, fr fr. 👑
  • gnutls_datum_t * responder_id — ignored, must be NULL. Not optional, not vibes-based. NULL or nothing. 💀
  • size_t responder_id_size — ignored, must be zero. Literally just put a 0 there and keep it pushing. 🙈
  • gnutls_datum_t * extensions — ignored, must be NULL. Same energy as responder_id. Don't get cute with it. ✨
Okay but notice how three out of four args are just... there? That's not a typo, that's a whole lore drop. Keep reading. 😭

🌸 DESCRIPTION 🌸

So here's the vibe: this function is for clients, and you use it to request an OCSP response from the server, using the "status_request" TLS extension. That's the whole point. 🫶

Only the OCSP status type is supported. Just the one. That's it. Periodt.

Now for the plot twist, because there lowkey always is one: previous versions of GnuTLS did let you set the responder_id and extensions fields. But because the semantics of how those parameters get used were genuinely difficult, plus some other issues, that support was removed since 3.6.0. So now those parameters must be set to NULL. No cap.

⚠️ Heads up: if you're on old code or old docs that show you passing real values into responder_id or extensions, that's the old way. Since 3.6.0 it's gone. Pass NULL, pass 0, and let the function do its thing. 🔥

💫 RETURNS 💫

On success, GNUTLS_E_SUCCESS (0) is returned. Otherwise you get a negative error code — which is the API's way of saying "not me catching an L". 😭

🦋 SINCE 🦋

3.1.3 — she's been around a minute, she's iconic, she's seen things. 👑

🙈 REPORTING BUGS 🙈

Found a bug? Don't just scream into the group chat, actually report it:

Copyright © 2001-2023 Free Software Foundation, Inc., and others.

Copying and distribution of this file, with or without modification, are permitted in any medium without royalty provided the copyright notice and this notice are preserved. So like, go off, just keep the receipts. 💜

⭐ SEE ALSO ⭐

The full documentation for gnutls is maintained as a Texinfo manual. If the /usr/share/doc/gnutls/ directory does not contain the HTML form, visit:

https://www.gnutls.org/manual/

And that's the page, bestie!! 🎀✨ This one's from gnutls 3.8.13, filed under gnutls_ocsp_status_request_enable_client(3) — go forth and request those OCSP responses responsibly. Slay. 💅💖

📦 where this page comes from