Lines Matching full:tls
57 .IX Title "OSSL-GUIDE-TLS-SERVER-BLOCK 7ossl"
58 .TH OSSL-GUIDE-TLS-SERVER-BLOCK 7ossl 2025-09-30 3.5.4 OpenSSL
64 ossl\-guide\-tls\-server\-block
65 \&\- OpenSSL Guide: Writing a simple blocking TLS server
66 .SH "SIMPLE BLOCKING TLS SERVER EXAMPLE"
67 .IX Header "SIMPLE BLOCKING TLS SERVER EXAMPLE"
69 simple, non-concurrent, TLS "echo" server application which accepts one client
77 The complete source code for this example blocking TLS server is available in
80 <https://github.com/openssl/openssl/blob/master/demos/guide/tls\-server\-block.c>.
83 already have some fundamental understanding of OpenSSL concepts and TLS (see
84 \&\fBossl\-guide\-libraries\-introduction\fR\|(7) and \fBossl\-guide\-tls\-introduction\fR\|(7));
96 TLS server. This method will automatically use TLS version negotiation to select
112 We would also like to restrict the TLS versions that we are willing to accept to
113 TLSv1.2 or above. TLS protocol versions earlier than that are generally to be
119 \& * TLS versions older than TLS 1.2 are deprecated by IETF and SHOULD
125 \& errx(res, "Failed to set the minimum TLS protocol version");
133 \& * Tolerate clients hanging up without a TLS "shutdown". Appropriate in all
135 \& * don\*(Aqt rely on TLS to defend against "truncation" attacks.
142 \& * limits on initial full TLS handshake or connection rates.
157 server certificate) are possible in TLS 1.2, they are rarely applicable, and
158 are not currently defined for TLS 1.3. Additional intermediate issuer CA
200 efficiently make additional TLS connections after completing an initial full
201 TLS handshake. With TLS 1.3, session resumption typically still performs a fresh
214 \& * How many client TLS sessions to cache. The default is
250 \& * require "mutual" TLS authentication (indeed there\*(Aqs no way to know
396 \&\fBossl\-guide\-libssl\-introduction\fR\|(7), \fBossl\-guide\-tls\-introduction\fR\|(7),
397 \&\fBossl\-guide\-tls\-client\-non\-block\fR\|(7), \fBossl\-guide\-quic\-client\-block\fR\|(7)