gnutls_record_recv(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

✨ gnutls_record_recv(3) ✨

okay bestie, welcome to the gnutls manual — this one's about gnutls_record_recv, an API function, and it's literally the moment you finally get to read the tea (the tea being bytes) that your TLS session has been holding for you 🫖💖

🌸 NAME 🌸

gnutls_record_recv — API function

🎀 SYNOPSIS 🎀

#include <gnutls/gnutls.h>

ssize_t gnutls_record_recv(gnutls_session_t session, void * data, size_t
data_size);

💅 ARGUMENTS 💅

  • gnutls_session_t session — bestie this is just a gnutls_session_t type. that's the whole vibe. it's your session, your main character 👑
  • void * data — the buffer that the data is gonna get read into. this is where the bytes get to live rent free 🏠✨
  • size_t data_size — the number of requested bytes. how many sips you're asking for 🥤

🦋 DESCRIPTION 🦋

so like, this function has similar semantics with recv() — same energy, same general idea. the only difference is that it accepts a GnuTLS session, and it uses different error codes. that's it, that's the twist 🌀

now for the spicy part 🌶️: in the special case that the peer requests a renegotiation, the caller will receive an error code of GNUTLS_E_REHANDSHAKE. and depending on who you are, you handle that differently:

  • if you're a client, this message may be simply ignored, replied with an alert GNUTLS_A_NO_RENEGOTIATION, or replied with a new handshake — it's literally up to the client's will. her choice, her call, periodt 💁‍♀️
  • if you're a server receiving this error code, you can only initiate a new handshake or terminate the session. no third option, no in-between, that's the rule 📜

and then there's the signal situation — if EINTR is returned by the internal pull function (the default is recv()), then GNUTLS_E_INTERRUPTED will be returned. and if GNUTLS_E_INTERRUPTED or GNUTLS_E_AGAIN comes back at you, you must call this function again to get the data. not optional, not a suggestion, just call it again bestie 🔁

also go peek at gnutls_record_get_direction() while you're here, it's the companion piece 💫

⭐ RETURNS ⭐

  • the number of bytes received, and zero on EOF (for stream connections)
  • a negative error code is returned in case of an error
  • and lowkey important: the number of bytes received might be less than the requested data_size. so don't be out here assuming you got the full scoop, check the return value fr fr 🙈

😭 REPORTING BUGS 😭

found a bug? not the vibe. report it to <bugs@gnutls.org>.

home page: https://www.gnutls.org

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. iconic behavior honestly 💖

🌈 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 whole page bestie, no cap 🧚✨ this was gnutls_record_recv(3) from the gnutls manual, version 3.8.13. go read some bytes, you ate 💅🍓

📦 where this page comes from