Home
last modified time | relevance | path

Searched refs:BIO_s_datagram (Results 1 – 18 of 18) sorted by relevance

/openssl/doc/man3/
H A DBIO_s_datagram.pod5 BIO_s_datagram, BIO_new_dgram,
19 BIO_METHOD *BIO_s_datagram(void);
33 BIO_s_datagram() is a BIO implementation designed for use with network sockets
43 BIO_s_datagram(), see L<BIO_s_dgram_pair(3)>.
47 When using BIO_s_datagram(), it is important to note that:
85 the BIO_s_datagram() to change.
89 Various controls are available for configuring the BIO_s_datagram() using
103 This informs the BIO_s_datagram() whether the underlying socket has been
107 If the I<peer> argument is non-NULL, BIO_s_datagram() assumes that the
143 modified by future calls to L<BIO_read(3)>, making use of BIO_s_datagram()
[all …]
H A DBIO_s_connect.pod112 created is a UDP datagram socket handled via L<BIO_s_datagram(3)>.
114 to an internal L<BIO_s_datagram(3)> instance. The created L<BIO_s_datagram(3)>
116 a pointer to the L<BIO_s_datagram(3)> instance to I<*dgram_bio>. The lifetime
117 of the internal L<BIO_s_datagram(3)> is managed by BIO_s_connect() and does not
H A DDTLSv1_listen.pod69 L<BIO_s_datagram(3)> is used, the peer address is updated when receiving a
79 L<BIO_s_datagram(3)>; see L<BIO_s_datagram(3)> for details on this issue.
/openssl/doc/man7/
H A Dopenssl-quic.pod142 L<BIO_s_datagram(3)>, recommended for most applications, replaces
167 a L<BIO_s_datagram(3)>. This is equivalent to instantiating a
168 L<BIO_s_datagram(3)> and using L<SSL_set0_rbio(3)> and L<SSL_set0_wbio(3)>.
184 network BIO provided to QUIC (such as a L<BIO_s_datagram(3)>) must be configured
191 L<BIO_s_datagram(3)> when used with QUIC, therefore applications which use this
343 Changes needed: Change your application to use L<BIO_s_datagram(3)> instead when
421 (such as L<BIO_s_datagram(3)>), the application can use
465 a network socket (e.g. via L<BIO_s_datagram(3)>) or whether it intends to buffer
660 semantics. It is implemented by L<BIO_s_datagram(3)> and L<BIO_s_dgram_pair(3)>.
742 a BIO abstracting a network socket such as L<BIO_s_datagram(3)>, or a BIO
[all …]
H A Dossl-guide-quic-client-block.pod169 bio = BIO_new(BIO_s_datagram());
184 Note the use of L<BIO_s_datagram(3)> here as opposed to L<BIO_s_socket(3)> that
186 instead of TCP for its transport layer. See L<BIO_new(3)>, L<BIO_s_datagram(3)>
H A Dossl-guide-quic-introduction.pod152 and is typically L<BIO_s_datagram(3)>, but other B<BIO> choices are available.
/openssl/demos/guide/
H A Dquic-client-block.c93 bio = BIO_new(BIO_s_datagram()); in create_socket_bio()
H A Dquic-client-non-block.c94 bio = BIO_new(BIO_s_datagram()); in create_socket_bio()
H A Dquic-multi-stream.c93 bio = BIO_new(BIO_s_datagram()); in create_socket_bio()
H A Dquic-hq-interop.c170 bio = BIO_new(BIO_s_datagram()); in create_socket_bio()
/openssl/util/
H A Dquicserver.c118 bio = BIO_new(BIO_s_datagram()); in create_dgram_bio()
H A Dmissingcrypto111.txt235 BIO_s_datagram(3)
H A Dlibcrypto.num1084 BIO_s_datagram 1112 3_0_0 EXIST::FUNCTION:DGRAM
/openssl/include/openssl/
H A Dbio.h.in536 /* BIO_s_datagram(), BIO_s_fd(), BIO_s_socket(), BIO_s_accept() and BIO_s_connect() */
773 const BIO_METHOD *BIO_s_datagram(void);
/openssl/crypto/bio/
H A Dbss_dgram.c248 const BIO_METHOD *BIO_s_datagram(void) in BIO_s_datagram() function
257 ret = BIO_new(BIO_s_datagram()); in BIO_new_dgram()
/openssl/doc/
H A Dbuild.info658 DEPEND[html/man3/BIO_s_datagram.html]=man3/BIO_s_datagram.pod
659 GENERATE[html/man3/BIO_s_datagram.html]=man3/BIO_s_datagram.pod
660 DEPEND[man/man3/BIO_s_datagram.3]=man3/BIO_s_datagram.pod
661 GENERATE[man/man3/BIO_s_datagram.3]=man3/BIO_s_datagram.pod
3174 html/man3/BIO_s_datagram.html \
3838 man/man3/BIO_s_datagram.3 \
/openssl/ssl/
H A Dssl_lib.c1660 return BIO_s_datagram(); in fd_method()
/openssl/
H A DCHANGES.md5458 The source/sink BIOs BIO_s_connect, BIO_s_accept and BIO_s_datagram

Completed in 169 milliseconds