TLS 1.0
TLS 1.0 API wrappers over the shared TLS 1.2-style context. Header: noxtls_tls10.h.
Deprecated and insecure
TLS 1.0 is deprecated and should not be used for new deployments. It is considered cryptographically weak by modern security standards and fails many compliance baselines.
Usage guidance
- Use TLS 1.0 only for controlled legacy interoperability where migration is not yet possible.
- Restrict exposure (segmented networks, allowlisted peers, short-term exception windows).
- Prefer upgrading peers to TLS 1.2 or TLS 1.3 as the primary remediation path.
Types
tls10_context_t
Alias of tls12_context_t specialized for TLS 1.0 operation.
API
Core lifecycle and I/O
noxtls_tls10_context_initnoxtls_tls10_context_freenoxtls_tls10_connectnoxtls_tls10_acceptnoxtls_tls10_sendnoxtls_tls10_recvnoxtls_tls10_close
Client handshake steps
noxtls_tls10_send_client_hellonoxtls_tls10_recv_server_hellonoxtls_tls10_recv_certificatenoxtls_tls10_recv_server_key_exchangenoxtls_tls10_recv_server_hello_donenoxtls_tls10_send_client_key_exchangenoxtls_tls10_send_change_cipher_specnoxtls_tls10_send_finishednoxtls_tls10_recv_change_cipher_specnoxtls_tls10_recv_finished
Server handshake steps
noxtls_tls10_recv_client_hellonoxtls_tls10_send_server_hellonoxtls_tls10_send_certificatenoxtls_tls10_send_server_key_exchangenoxtls_tls10_send_server_hello_donenoxtls_tls10_recv_client_key_exchangenoxtls_tls10_recv_change_cipher_spec_clientnoxtls_tls10_recv_finished_clientnoxtls_tls10_send_change_cipher_spec_servernoxtls_tls10_send_finished_server
For shared structures and record constants, see TLS (common).