SSL_RSTATE_STRING(3)

💖 NAME 💖

okay so this is the SSL_RSTATE_STRING(3) page, hanging out in the Library Functions Manual 💅 and it's all about SSL_rstate_string and SSL_rstate_string_long — the two functions that get you a textual description of the state of an SSL object during a read operation. slay.

---

✨ SYNOPSIS ✨

bestie, you're pulling this in from the library “libssl” libcrypto crew, and you include #include <openssl/ssl.h> — then the calls look exactly like this:

const char *
SSL_rstate_string(SSL *ssl);

const char *
SSL_rstate_string_long(SSL *ssl);

---

🦋 DESCRIPTION 🦋

SSL_rstate_string() returns a 2-letter string indicating the current read state of the SSL object ssl. short and cute, iykyk.

SSL_rstate_string_long() returns a string indicating the current read state of the SSL object ssl. the longer, chattier version 💬.

when you're performing a read operation, the SSL/TLS engine must parse the record, consisting of header and body. both. the whole thing. when working in a blocking environment, SSL_rstate_string[_long]() should always return "RD"/"read done" — periodt.

this function should only seldom be needed in applications. like, genuinely, it's not the main character of your app's needs 🙈.

---

🔥 RETURN VALUES 🔥

SSL_rstate_string() and SSL_rstate_string_long() can return the following values:

• "RH"/"read header" — the header of the record is being evaluated. we're looking at the header bestie.
• "RB"/"read body" — the body of the record is being evaluated. now we're in the body era.
• "RD"/"read done" — the record has been completely processed. finished. ate. 💅
• "unknown"/"unknown" — the read state is unknown. this should never happen 💀 like fr fr, never.

---

👀 SEE ALSO 👀

• ssl(3)

---

🌸 HISTORY 🌸

SSL_rstate_string() and SSL_rstate_string_long() first appeared in SSLeay 0.6.0 and have been available since OpenBSD 2.4. iconic lineage honestly 👑

---

mwah 💋 this page's cute little footer says Debian, June 8, 2025 — that's the source/version and date, bestie 🫶✨