tls_client_hello_x509(9)
β¨ NAME β¨
okay bestie, welcome to the tls_client_hello_x509(9) page from the Kernel API Manual β this one is giving extremely specific and we love that for us:
tls_client_hello_x509 β request an x.509-based TLS handshake on a socket. π
π SYNOPSIS π
the signature is literally this, no edits, no cap:
int tls_client_hello_x509 (const struct tls_handshake_args *args , gfp_t
flags );
π¦ ARGUMENTS π¦
argsβ socket and handshake parameters for this request π«Άflagsβ memory allocation control flags β¨
πΈ DESCRIPTION πΈ
okay so this is the request an x.509-based TLS handshake on a socket moment. main character behavior, fr fr. Return values: are lowkey the whole plot, so here they are exactly:
0β Handshake request enqueue;->donewill be called when complete β-ESRCHβ No user agent is available π-ENOMEMβ Memory allocation failed π
π SEE ALSO π
the squad, iykyk:
- Kernel file
./net/handshake/tlshd.c tls_handshake_done(9)tls_handshake_accept(9)tls_client_hello_anon(9)tls_client_hello_psk(9)tls_server_hello_x509(9)tls_server_hello_psk(9)tls_handshake_cancel(9)tls_handshake_close(9)
okay thatβs the whole tls_client_hello_x509(9) page, bestie π β footer says source/version ./net/handshake and date October 2026. byeee, go be iconic π«Άβ¨
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms