tls_client_hello_anon(9)

✨ tls_client_hello_anon ✨

okay bestie, welcome to the tls_client_hello_anon page from the Kernel API Manual — yes it's a kernel manpage, yes it's section 9, yes we're gonna get through it together 💖

---

🦋 NAME 🦋

tls_client_hello_anon — the move where you ask a socket for a whole anonymous TLS handshake. no certs, no names, just vibes 💅

---

🌸 SYNOPSIS 🌸

int tls_client_hello_anon (const struct tls_handshake_args *args , gfp_t
flags );

like, that's the whole signature. she's compact, she's iconic 🎀

---

🫶 ARGUMENTS 🫶

• args — the socket and the handshake parameters for this request. everything you need to describe the ask lives in here ✨
• flags — the memory allocation control flags. this is the "how am i allowed to allocate while doing this" knob 🧚

---

👑 DESCRIPTION 👑

ok so this is the part where we talk return values, and honestly the return values here are the description. read them carefully bestie, no skimming 🙈

• 0 — handshake request enqueue. yup, that's the slay case. once it's all done, ->done will be called when complete 🔥
• -ESRCH — no user agent is available. like, nobody's home to handle it 😭
• -ENOMEM — memory allocation failed. the allocation did not eat, and neither did you 💀

ngl the negative ones are just facts of life, but now you know exactly what each one means, so vibe check passed 🫶

---

🌈 SEE ALSO 🌈

kernel file ./net/handshake/tlshd.c, plus the whole friend group:

• tls_handshake_done(9)
• tls_handshake_accept(9)
• tls_client_hello_x509(9)
• tls_client_hello_psk(9)
• tls_server_hello_x509(9)
• tls_server_hello_psk(9)
• tls_handshake_cancel(9)
• tls_handshake_close(9)

they're all linked, they all matter, go read them if you're obsessed (you should be) 💜

---

and that's the page, bestie 🎀 this one lives under ./net/handshake and it's dated October 2026 — so mark your calendar, screenshot the footer, and go request that anonymous handshake. periodt ✨🦋💖