Home
last modified time | relevance | path

Searched refs:connected (Results 1 – 23 of 23) sorted by relevance

/openssl/doc/man3/
H A DBIO_s_datagram.pod53 This BIO can be used with either a connected or unconnected network socket. A
54 connected socket is a network socket which has had L<BIO_connect(3)> or a
63 to become connected. These controls are provided to indicate to the BIO how
75 BIO_s_dgram() only with a connected socket, or, if using BIO_s_dgram() with an
99 connected.
104 connected, and therefore how the BIO_s_datagram() should attempt to use the
108 underlying socket has been connected and will attempt to use the socket using OS
111 is connected.
114 socket is not connected and will attempt to use the socket using an OS APIs
154 connected. Other BIOs may also implement this control if they are capable of
[all …]
H A DDTLSv1_listen.pod65 the peer and continue the handshake in a connected state.
70 datagram on an unconnected socket. If the socket is not connected, it can
81 Once a socket has been connected, L<BIO_ctrl_set_connected(3)> should be used to
82 inform the BIO that the socket is to be used in connected mode.
H A DSSL_get_rbio.pod28 No BIO was connected to the SSL object
H A DBIO_s_bio.pod57 BIO_make_bio_pair() joins two separate BIOs into a connected pair.
59 BIO_destroy_pair() destroys the association between two connected BIOs. Freeing
74 BIO_set_write_buf_size() to create a connected pair of BIOs B<bio1>, B<bio2>
H A DBIO_s_connect.pod150 the underlying socket has connected and retry the call.
169 BIO_get_conn_hostname() returns the connected hostname or NULL if
174 BIO_get_conn_port() returns a string representing the connected
H A DBIO_s_dgram_pair.pod47 L<BIO_make_bio_pair(3)> and L<BIO_set_write_buf_size(3)> to create a connected
55 L<BIO_destroy_bio_pair(3)> destroys the association between two connected BIOs.
80 connected to a peer BIO.
H A DSSL_set_fd.pod30 If there was already a BIO connected to B<ssl>, BIO_free() will be called
H A DSSL_CTX_set_ssl_version.pod41 When L<SSL_clear(3)> is called and no session is connected to
H A DOCSP_sendreq_new.pod51 I<io> should haven been connected to host C<example.com> on port 80 and I<path>
H A DSSL_CTX_add1_chain_cert.pod90 If B<ssl> is a server and has sent a certificate to a connected client
H A DSSL_get_error.pod121 called again later. The underlying BIO was not connected yet to the peer
H A DUI_new.pod114 that's connected to it, like duplicated input strings, results and others.
/openssl/demos/sslecho/
H A DREADME.md17 - Once connected with TCP, the client 'upgrades' to SSL using
/openssl/ssl/quic/
H A Dquic_tserver.c50 unsigned int connected : 1; member
216 srv->connected = 1; in ossl_quic_tserver_tick()
/openssl/crypto/bio/
H A Dbss_dgram.c212 unsigned int connected; member
426 if (!data->connected && ret >= 0) in dgram_read()
448 if (data->connected) in dgram_write()
584 data->connected = 1; in dgram_ctrl()
735 data->connected = 1; in dgram_ctrl()
738 data->connected = 0; in dgram_ctrl()
1082 if (data->connected == 0) { in translate_msg()
/openssl/doc/man7/
H A Dossl-guide-tls-client-block.pod143 Once the socket is constructed it must be connected to the remote server. Again
204 /* We have a connected socket so break out of the loop */
222 Once the socket has been created and connected we need to associate it with a
257 We have already connected our underlying socket to the server, but the client
267 failure, or we may get connected to the "default" server which may not be the
H A Dossl-guide-quic-client-block.pod163 As for our TLS client, once the socket has been created and connected we need to
224 is being connected to. In L</Creating the socket and BIO> above we saved that
H A Dossl-guide-tls-introduction.pod183 Once the command has connected type the letter "Q" followed by "<enter>" to exit
/openssl/Configurations/
H A DREADME-design.md4 How are things connected?
/openssl/doc/designs/quic-design/
H A Dquic-fault-injector.md500 * connected to.
H A Dquic-api.md1635 client is connected to a compatible server but may result in strange
1636 inconsistencies of QUIC internal state if a client is accidentally connected to
/openssl/include/openssl/
H A Dbio.h.in110 # define BIO_CTRL_DGRAM_SET_CONNECTED 32/* allow for an externally connected
/openssl/
H A DCHANGES.md5987 can be used to reveal up to 64k of memory to a connected client or
8935 can be used to reveal up to 64k of memory to a connected client or

Completed in 96 milliseconds