Home
last modified time | relevance | path

Searched refs:which (Results 1 – 25 of 586) sorted by relevance

12345678910>>...24

/openssl/doc/designs/quic-design/
H A Dquic-thread-assist.md12 per-connection mutex for the duration of any public API call which we forward to
27 can process some event which causes mutation of `foo`.
43 It would also only be required for applications which want to use thread
58 - The assist thread performs a reduced tick operation which does everything
60 future which would be processed by the handshake layer.
65 which doesn't need to be acknowledged and isn't “urgent”. The other
74 handshake completion (which would in itself be highly unusual), we simply
90 which would forward to the HL after connection commences (specifically, after
98 setters, focus on APIs which return data which doesn't change after
100 enabled. Some APIs may not have ways to indicate failure; for such APIs which
H A Dglossary.md7 **Active Stream:** A stream which has data or control frames ready for
38 another QUIC packet which is to be coalesced with one or more previous QUIC
113 **MinPPL:** The minimum number of bytes which must be placed into a packet
122 the size of any AEAD authentication tag which will be attached to the
126 in which API calls can be made on different threads.
129 usage in which API calls must not be made concurrently.
212 frame which was transmitted. See FIFM design document for details.
221 store data which has been RX'd but not yet read by the application.
251 **SRTM:** Stateless reset token manager. Object which tracks SRTs we have
255 data which has been passed to libssl for sending but which has not yet been
[all …]
H A Dquic-io-arch.md13 The [requirements for QUIC](./quic-requirements.md) which have formed the basis
63 libssl, which will support both blocking and non-blocking I/O.
114 have a BIO interface which provides for select(3)-like functionality or which
135 - a thread which exists solely to wait for and dispatch timeout events.
169 aligns optimally to non-blocking I/O and which cannot be accommodated
366 which can be used for synchronisation, or when we are dealing with an
374 - A pollable BIO is a BIO which can provide some kind of OS-level
375 synchronisation primitive, which can be used to determine when
386 APIs on these platforms which have other handle spaces. However, this
393 for the purposes of this API, which will never return. Instead, the
[all …]
H A Ddgram-api.md4 We need to evolve the API surface of BIO which is relevant to BIO_dgram (and the
5 eventual BIO_dgram_mem) to support APIs which allow multiple datagrams to be
23 on OSes which do not support `sendmmsg` or `sendmsg`.
28 - We do not have to expose functionality which we cannot guarantee
32 which would pollute the environment of applications which include
169 Options which were considered
172 Options for the API surface which were considered included:
208 - We would need to include the OS headers which provide these
265 have an alternate code path which doesn't rely on them?
292 BIO_dgram which is 1 by default, which can be increased by a call to a
[all …]
H A Dquic-fc.md10 which the relevant flow control limit is expressed as the maximum number of
61 - **Controlled bytes** refers to any byte which counts for purposes of flow
65 - (RX side only) **Retirement**, which refers to where we dequeue one or more
82 - The **Credit Watermark** (CWM), which is the number of bytes which have
86 - The available **credit**, which is always simply the difference between
89 - (RX side only) The **threshold**, which is how close we let the RWM
93 - (RX side only) The **window size**, which is the amount by which we or a peer
103 - If any circumstance occurs which would cause the SWM to exceed the CWM,
143 value which would be returned by the Get TX Window function changes from
245 frame, which may after all duplicate some of the controlled bytes in a
[all …]
H A Dquic-fifm.md4 The QUIC frame-in-flight manager is responsible for tracking frames which were
5 sent which need to be regenerated if the packets they were placed into are
84 most control frames which do not have special requirements.
90 data bytes for each (which may not be one contiguous range).
96 (which may not be one contiguous range), for similar reasons.
126 - The frame type, which is provided by the caller along with the buffer.
131 - A state, which is either `NEW` or `TX`. Frames added to the CFQ have
287 - Keeping track of all GCR control frames which were transmitted
428 - It references a TXPIM which manages each `QUIC_TXPIM_PKT`;
434 to a given stream, in which case a stream ID is specified.
[all …]
/openssl/doc/man3/
H A DSSL_poll.pod82 which designates a resource which is being polled for readiness, and a set of
83 event flags which indicate the specific readiness events which the caller is
104 This is the set of zero or more events which the caller is interested in
111 After SSL_poll() returns, this is the set of zero or more events which are
187 distinct from an exception condition reported on a resource which was
205 This event is never raised on objects which are not connections.
214 This event is never raised on objects which are not connections.
289 Calls to SSL_poll() which specify another value, or which pass I<timeout> as
332 "Normal" events representing exceptional I/O conditions which do not
361 raised in I<revents>. The entries added to the ERR stack (of which there is
[all …]
H A DSSL_get_stream_id.pod26 SSL object, or for a QUIC connection SSL object which has a default stream
48 default stream attached), and that stream is a unidirectional QUIC stream which
54 default stream attached), and that stream is a unidirectional QUIC stream which
82 SSL object which is not a QUIC SSL object, or if called on a QUIC connection SSL
88 SSL_is_stream_local() returns 1 if called on a QUIC stream SSL object which
89 represents a stream which was locally initiated. It returns 0 if called on a
90 QUIC stream SSL object which represents a stream which was remotely initiated by
H A DBIO_get_rpoll_descriptor.pod5 BIO_get_rpoll_descriptor, BIO_get_wpoll_descriptor - obtain a structure which
28 which represents some kind of OS or non-OS resource which can be used to
31 BIO_get_rpoll_descriptor() outputs a descriptor which can be used to determine
33 outputs a descriptor which can be used to determine when the BIO can
40 resource which might be represented by a poll descriptor is an OS file
41 descriptor which can be used with APIs such as select().
62 sockets, which may vary by OS. For example, on Windows, the value is a B<SOCKET>
H A DSSL_get_event_timeout.pod28 The SSL object has events which need to be handled immediately; The fields of
33 The SSL object has events which need to be handled after some amount of time
34 (relative to the time at which SSL_get_event_timeout() was called). I<*tv> is
35 set to the amount of time after which L<SSL_handle_events(3)> should be called
40 There are currently no timer events which require handling in the future. The
58 internal processing which is due; for more information, see
H A DBIO_s_datagram.pod34 which provide datagram semantics, such as UDP sockets. It is suitable for use
42 For a memory-based BIO which provides datagram semantics identical to those of
54 connected socket is a network socket which has had L<BIO_connect(3)> or a
109 APIs which do not specify peer addresses (for example, send(3) and recv(3) or
115 which specify peer addresses (for example, sendto(3) and recvfrom(3)).
122 This outputs a B<BIO_ADDR> which specifies one of the following values,
153 to try and autodetect the peer address to which the underlying socket is
172 estimate the final size of the Layer 3 (e.g. IP) packet which will contain the
173 datagram. In most cases, the maximum datagram payload size which can be
187 Fragment mode, in which datagrams will be set with the IP Don't Fragment (DF)
[all …]
H A DX509_add_cert.pod21 The I<certs> argument may be NULL, which implies no effect.
27 which is used to control details of the operation.
29 The value B<X509_ADD_FLAG_DEFAULT>, which equals 0, means no special semantics.
39 which is determined using L<X509_cmp(3)>, are ignored.
42 which is determined using L<X509_self_signed(3)>, are ignored.
H A DCMS_get0_RecipientInfos.pod53 identifier associated with a specific CMS_RecipientInfo structure B<ri>, which
58 CMS_RecipientInfo structure B<ri>, which must be of type CMS_RECIPINFO_TRANS.
62 the CMS_RecipientInfo structure B<ri>, which must be of type
66 and peer certificate B<peer> with the CMS_RecipientInfo structure B<ri>, which
70 CMS_RecipientInfo structure B<ri>, which must be of type CMS_RECIPINFO_AGREE.
73 CMS_RecipientInfo structure B<ri> which must be of type CMS_RECIPINFO_KEK. Any
84 which must be of type CMS_RECIPINFO_KEK. It returns zero if the comparison is
88 B<keylen> with the CMS_RecipientInfo structure B<ri>, which must be of type
H A DSSL_CTX_set_session_id_context.pod5 SSL_CTX_set_session_id_context, SSL_set_session_id_context - set context within which session can b…
19 B<sid_ctx_len> within which a session can be reused for the B<ctx> object.
22 B<sid_ctx_len> within which a session can be reused for the B<ssl> object.
29 application), which might lead to malfunctions. Therefore, each application
30 must set its own session id context B<sid_ctx> which is used to distinguish
H A DSSL_handle_events.pod15 SSL_handle_events() performs any internal processing which is due on an SSL object. The
18 timeout events which have become due, or may attempt, to the extent currently
22 The primary use case for SSL_handle_events() is to allow an application which uses
38 applications which do not require support for OpenSSL 3.1 or older.
43 L<SSL_write(3)>. Note that this is different to QUIC which also performs event
48 Using SSL_handle_events() on an SSL object which represents a QUIC connection allows
H A DOSSL_HTTP_REQ_CTX.pod67 which gets populated with the B<BIO> to write/send the request to (I<wbio>),
68 the B<BIO> to read/receive the response from (I<rbio>, which may be equal to
74 which collects the HTTP request header lines.
82 which should be 1 to indicate C<POST> or 0 to indicate C<GET>.
118 be used directly to read the response contents, which may support streaming.
125 L<OSSL_HTTP_open(3)> with the default being 0, which means no timeout.
137 even if a GET request is going to be sent, in which case I<req> must be NULL.
149 The function may need to be called again if its result is -1, which indicates
154 in addition parses the response, which must be a DER-encoded ASN.1 structure,
164 which may support streaming.
[all …]
H A DSSL_get_value_uint.pod97 may represent connection parameters which do not participate in explicit
111 example, after a connection has been established, for a value which cannot be
130 Values in this value class are read-only, and represent the value which was
137 to be used prior to completion of feature negotiation, in which case that value
256 A call to SSL_set_value_uint() which causes this value to switch back to the
259 SSL_set_value_uint() which causes this value to switch to the explicit event
265 confined to state which relates to only that object. For example, if you
286 in the write buffer which have yet to be acknowledged by the peer. Successful
287 calls to L<SSL_write_ex(3)> which accept data cause this number to increase.
296 calls to L<SSL_write_ex(3)> which accept data cause this number to decrease.
[all …]
/openssl/doc/designs/ddd/
H A DREADME.md7 agreed. One significant dimension which must be considered when considering any
9 uses the APIs which exist today, as this determines the ways in which those
10 applications will be affected by any proposed changes, the extent to which they
11 will be affected, and the extent of any changes which will need to be made by
16 the usage patterns common in codebases which use OpenSSL, so that it can
18 directory seeks to maintain a set of **API usage demos** which demonstrate a
19 full spectrum of ways in which real-world applications use the OpenSSL APIs.
29 a present body of understanding of API usage patterns, which can be used to plan
42 The demos also deliberately focus on aspects of libssl usage which are likely to
61 patterns were determined and used to determine categories into which to classify
[all …]
/openssl/doc/man7/
H A Dopenssl-quic.pod21 mode, which is intended to provide compatibility with existing non-QUIC
45 requirements, which existing applications should bear in mind;
49 Aspects which must be considered by existing applications when adopting QUIC,
50 including potential changes which may be needed.
426 Applications which use thread assisted mode do not need to be concerned
482 the APIs listed under B<QUIC-SPECIFIC APIS> which provide access to
605 Provides information on the kind of QUIC stream which is attached
648 This is a new BIO method which is similar to a conventional BIO pair but
659 This is a new BIO API which can be implemented by BIOs which implement datagram
727 a structure which expresses some kind of OS resource which can be used to
[all …]
/openssl/doc/internal/man3/
H A DDEFINE_LIST_OF.pod51 B<I<TYPE>>. This is a structure which should be treated as opaque.
60 to zero which creates an empty list.
63 to by I<elem> to zero which allows it to be used in lists.
79 B<ossl_list_I<TYPE>_insert_head>() inserts the element I<elem>, which
82 B<ossl_list_I<TYPE>_insert_tail>() inserts the element I<elem>, which
86 which must not be in the list, into the I<list> immediately before the
90 which must not be in the list, into the I<list> immediately after the
H A Dossl_cmp_mock_srv_new.pod46 I<propq>, both of which may be NULL to select the defaults.
66 ossl_cmp_mock_srv_set1_newWithNew() sets the value (which may be NULL)
69 ossl_cmp_mock_srv_set1_newWithOld() sets the value (which may be NULL)
72 ossl_cmp_mock_srv_set1_oldWithNew() sets the value (which may be NULL)
79 A I<bodytype> of -1 can be used to disable this feature, which is the default.
/openssl/ssl/
H A Dtls13_enc.c448 int tls13_change_cipher_state(SSL_CONNECTION *s, int which) in tls13_change_cipher_state() argument
488 if (((which & SSL3_CC_CLIENT) && (which & SSL3_CC_WRITE)) in tls13_change_cipher_state()
489 || ((which & SSL3_CC_SERVER) && (which & SSL3_CC_READ))) { in tls13_change_cipher_state()
490 if ((which & SSL3_CC_EARLY) != 0) { in tls13_change_cipher_state()
583 } else if (which & SSL3_CC_HANDSHAKE) { in tls13_change_cipher_state()
619 if (which & SSL3_CC_HANDSHAKE) { in tls13_change_cipher_state()
638 if ((which & SSL3_CC_EARLY) == 0) { in tls13_change_cipher_state()
718 if ((which & SSL3_CC_WRITE) != 0) { in tls13_change_cipher_state()
725 level = (which & SSL3_CC_EARLY) != 0 in tls13_change_cipher_state()
727 : ((which &SSL3_CC_HANDSHAKE) != 0 in tls13_change_cipher_state()
[all …]
/openssl/Configurations/
H A D15-android.conf107 if (which("clang") =~ m|^$ndk/.*/prebuilt/([^/]+)/|) {
122 if (which("llvm-ar") =~ m|^$ndk/.*/prebuilt/([^/]+)/|) {
134 if (which("$triarch-$cc") !~ m|^$ndk|) {
142 if (which("$triarch-gcc") !~ m|^$ndk/.*/prebuilt/([^/]+)/|) {
/openssl/external/perl/Text-Template-1.56/
H A DChanges11 - Skip/todo tests which fail under Devel::Cover (Thanks Roy Ivy)
84 Text::Template->append_text_to_output method, which Text::Template always
94 - _scrubpkg, which was responsible for eptying out temporary packages after
129 Note that the default message used to report the line number at which the
130 program fragment began; it now reports the line number at which the error
155 call; this is a function which receives each code fragment prior to
156 evaluation, and which may modify and return the fragment; the modified
159 line number of the template at which the error occurred:
177 line number of the template at which the error occurred:
187 function which receives each code fragment prior to evaluation, and which
[all …]
/openssl/.github/ISSUE_TEMPLATE/
H A Ddocumentation.md10 Please remember to tell us which OpenSSL version you are using and then
12 (e.g., in which manual page). If you are missing the documentation for a

Completed in 56 milliseconds

12345678910>>...24