Lines Matching +full:many +full:- +full:to +full:- +full:one

1 .\" -*- mode: troff; coding: utf-8 -*-
35 .\" entries marked with X<> in POD.  Of course, you'll have to process the
57 .IX Title "OSSL-GUIDE-LIBSSL-INTRODUCTION 7ossl"
58 .TH OSSL-GUIDE-LIBSSL-INTRODUCTION 7ossl 2025-09-30 3.5.4 OpenSSL
60 .\" way too many mistakes in technical documents.
64 ossl\-guide\-libssl\-introduction, ssl
65 \&\- OpenSSL Guide: An introduction to libssl
72 operations (see \fBossl\-guide\-libcrypto\-introduction\fR\|(7)).
75 network protocols, so a developer familiar with writing applications using one
76 of these protocols should be able to transition to using another with relative
79 An application written to use \f(CW\*(C`libssl\*(C'\fR will include the \fI<openssl/ssl.h>\fR
83 An \fBSSL\fR object is used to represent a connection to a remote peer. Once a
93 stream is guaranteed to be delivered in order without any data loss. A stream
94 can be uni\- or bi-directional.
96 SSL/TLS only supports one stream of data per connection and it is always
97 bi-directional. In this case the \fBSSL\fR object used for the connection also
98 represents that stream. See \fBossl\-guide\-tls\-introduction\fR\|(7) for more
102 uni\- or bi-directional. In this case an \fBSSL\fR object can represent the
104 a separate \fBSSL\fR object is used for each one. See
105 \&\fBossl\-guide\-quic\-introduction\fR\|(7) for more information.
107 An \fBSSL_CTX\fR object is used to create the \fBSSL\fR object for the underlying
108 connection. A single \fBSSL_CTX\fR object can be used to create many connections
109 (each represented by a separate \fBSSL\fR object). Many API functions in libssl
110 exist in two forms: one that takes an \fBSSL_CTX\fR and one that takes an \fBSSL\fR.
111 Typically settings that you apply to the \fBSSL_CTX\fR will then be inherited by
113 directly to the \fBSSL\fR object without affecting other \fBSSL\fR objects. Note that
114 you should not normally make changes to an \fBSSL_CTX\fR after the first \fBSSL\fR
119 that an application may need to use. They are summarised below.
122 This structure is used to indicate the kind of connection you want to make, e.g.
123 whether it is to represent the client or the server, and whether it is to use
129 can be reused to create future connections with the same peer more rapidly. The
137 algorithms they are going to use for encryption and other uses. A single set
138 of cryptographic algorithms that are to be used together is known as a
145 See \fBossl\-guide\-tls\-introduction\fR\|(7) for an introduction to the SSL/TLS
146 protocol and \fBossl\-guide\-quic\-introduction\fR\|(7) for an introduction to QUIC.
148 See \fBossl\-guide\-libcrypto\-introduction\fR\|(7) for an introduction to \f(CW\*(C`libcrypto\*(C'…
151 \&\fBossl\-guide\-libcrypto\-introduction\fR\|(7), \fBossl\-guide\-tls\-introduction\fR\|(7),
152 \&\fBossl\-guide\-quic\-introduction\fR\|(7)
155 Copyright 2000\-2025 The OpenSSL Project Authors. All Rights Reserved.