Searched refs:received (Results 1 – 25 of 110) sorted by relevance
12345
17 Buffers for stream data to be sent or received from the peer over the73 and to record the statistics of the received stream data.102 Packets are received from the network through the Datagram BIO interface.117 A module that tracks packets sent to the peer and received ACK frames.118 It detects lost packets (after an ACK is not received in time). It informs119 TX packetizer that it can drop frames waiting to be ACKed when ACK is received.124 be sent for the received packets.130 which makes it a special kind of module. It dispatches the received packets133 _For client side and MVP this module just checks that the received packet has
4 This is a QUIC specific module that retains the received stream data13 - As packets with stream frames are received in arbitrary frames the14 received data must be stored until all the data with earlier offsets15 are received.16 - As packets can be received before application calls SSL_read() to read26 or fully overlapping data with previously received frames.35 the received data should not be copied out of the decrypted packets to99 The QUIC_RSTREAM object holds the received stream data in the SFRAME_LIST101 data frames. Each list item holds a pointer to the received packet102 wrapper for refcounting and proper release of the received packet
8 - Handling received ACK frames18 received25 - be notified of all received datagrams26 - be notified of all received packets27 - be notified of all received ACK frames194 This must be called whenever a datagram is received. A datagram may contain223 /* The packet number of the received packet. */226 /* The time at which the packet was received. */240 * to the received packet. If unknown, use OSSL_ACKM_ECN_NONE.250 This must be called whenever an ACK frame is received. It should be called[all …]
106 Initial packet to the server and received at least one valid Initial packet124 - Handshake Continued: The client has received and successfully135 parties have sent and received (and verified) TLS 1.3 Finished143 (Though the peer's QUIC Transport Parameters may have been received155 - Handshake Confirmed: The client has received confirmation from176 an immediate close (i.e., a `CONNECTION_CLOSE` frame is received);192 transmitted again in response to any packets received. This ensures193 that a `CONNECTION_CLOSE` frame is received by the peer even if the469 - `RX:ANY[CONNECTION_CLOSE]` denotes a `CONNECTION_CLOSE` frame received552 - `RX:VER_NEG`: Only valid if we have not yet received any successfully[all …]
46 received crypto frame data may be consumed, or new crypto frame data may be138 `transport_params` argument. When the peer's parameters are received the213 Receive Buffers" when it is received by the peer. However the TLS implementation233 callback when the transport parameters have been received from the peer.
35 protocol messages (such as handshake messages) that are received or54 This flag is B<0> when a protocol message has been received and B<1>82 The B<SSL> object that received or sent the message.104 If processing a received protocol message results in an error,111 a TLS 1.0 ClientHello message is received by an SSL 3.0-only server,126 Used when an encrypted TLSv1.3 record is sent or received. In encrypted TLSv1.3133 Used when a QUIC datagram is sent or received.137 Used when a QUIC packet is sent or received.141 Used when a QUIC frame is sent or received. This is only used for non-crypto146 Used when a QUIC stream data or crypto frame is sent or received. Only the QUIC[all …]
5 SSL_inject_net_dgram - inject a datagram as though received from the network19 object. The payload is processed as though it was received from the network.29 the injected packet was not actually received from the network directly by30 OpenSSL, the packet will be processed as though the received datagram had the
96 Otherwise (when according to I<ctx> a 'waiting' status has been received before)103 and returns -1 after assigning the received checkAfter value137 and returns the list of B<ITAV>s received in a genp response message.146 On success it assigns to I<*out> the list of certificates received,155 On success it assigns to I<*newWithNew> the root certificate received.171 On success it assigns to I<*crl> the CRL received.178 the certificate template received. NULL output means that no certificate181 if received, otherwise it set to NULL.214 in case a 'waiting' status has been received and checkAfter value is available.217 assign the received value unless I<checkAfter> is NULL.[all …]
5 SSL_get0_peer_scts - get SCTs received16 been received. If this is the first time that this function has been called for
38 A shutdown alert was received form the peer, either a normal close_notify56 If a close_notify was received, SSL_RECEIVED_SHUTDOWN will be set,73 has been received from the peer or the QUIC connection is fully terminated
63 A close_notify shutdown alert message is received from the peer.106 second and subsequent call, once a corresponding message is received from the112 received from the peer, or because a close_notify alert message needs to be sent120 received).124 B<SSL_ERROR_ZERO_RETURN>. This ensures any data received immediately before the199 when all data has been received.216 received and processed by OpenSSL.264 to ensure that all transmitted data was received by the peer. This is unlike a270 be received by the peer.307 successfully received. However, a consequence of this is that a fully[all …]
78 An inappropriate message was received. This alert is always fatal84 This alert is returned if a record is received with an incorrect89 The decompression function received improper input (e.g. data139 A TLSCiphertext record was received which had a length more than145 A valid certificate chain or partial chain was received, but the152 A valid certificate was received, but when access control was
34 B<SSL_ERROR_WANT_ASYNC> has been received - see L<SSL_get_error(3)>). Typically46 B<SSL_ERROR_WANT_ASYNC> was received (or since the B<SSL> object was created if47 no B<SSL_ERROR_WANT_ASYNC> has been received). Similar to SSL_get_all_async_fds()
131 order that they were received in the Certificate message.139 met and the corresponding extension was received in the ClientHello. That is, if140 no corresponding extension was received in the ClientHello then B<add_cb> will256 be used to store the extension data received in a convenient structure or259 If the same custom extension type is received multiple times a fatal261 is received in a ServerHello/EncryptedExtensions message which was not sent in264 only called if the corresponding extension was received in the ClientHello. This
46 the data to send, or to be filled with a received message. I<data_len> should be50 actual amount of data sent or received.65 on a per-datagram basis, and the source address of received datagrams to be68 datagrams, and written by BIO_recvmmsg() with the source address of received73 of received datagrams to be determined. Unlike I<peer>, support for I<local>83 system does not report a local address for a specific received message, the85 This is known to happen on Windows when a packet is received which was sent by
17 Data is received in whole blocks known as records from the peer. A whole record42 not yet processable (e.g. because OpenSSL has only received a partial record so
340 validating signature-based protection in received CMP messages.355 Do not cache certificates received in the extraCerts CMP message field.489 in received CMP messages unless B<OSSL_CMP_OPT_NO_CACHE_EXTRACERTS> is set.647 which have been augmented by the list of extraCerts received.651 and if this fails it takes the received extraCerts as fallback.686 the last received CertRepMessage or Revocation Response or error message:713 of the last received CertRepMessage or Revocation Response or error message,732 been called) on the last received certificate response message IP/CP/KUP.735 X.509 certificates in the caPubs field of the last received certificate737 or an empty stack if no caPubs have been received in the current transaction.[all …]
20 ClientHello is received that does not contain a cookie, then they respond with a22 received with a cookie that is verified then the function returns in order to57 When a ClientHello is received that contains a cookie that has been verified,122 received from a peer. Errors may be placed on the OpenSSL error queue with
40 corresponding ACK has been received yet from the peer. This can have performance45 been received for the final handshake message.
45 The read functions work based on the SSL/TLS records. The data are received in47 completely received, can it be processed (decryption and check of integrity).53 Only when the record has been received and processed completely will the read
20 is called whenever TLS key material is generated or received, in order to allow
7 - generic checks on a received CMP message, updating the context64 records in B<ctx> the senderNonce of the received message as the new recipNonce
19 - When the SSL connection completes, data is sent and received using
62 int packet_space, OSSL_TIME received, in depack_do_frame_ack() argument127 packet_space, received)) in depack_do_frame_ack()1047 OSSL_TIME received, OSSL_ACKM_RX_PKT *ackm_data) in depack_process_frames() argument1130 if (!depack_do_frame_ack(pkt, ch, packet_space, received, in depack_process_frames()
250 Upon receipt of the General Response, information about all received276 received in a genp message with id-it-certReqTemplate.283 Note: any keySpec field contents received are logged as INFO.730 If present and the optional oldWithNew certificate is received,737 received in a genp message of type C<rootCaKeyUpdate>.741 Any received newWithNew certificate is verified755 received in a genp message of infoType C<rootCaKeyUpdate>.761 received in a genp message of infoType C<rootCaKeyUpdate>.779 The file to save CRL received in a genp message of infoType C<crls>.1121 These have been received from the server unless B<-rspin> takes effect.[all …]
Completed in 36 milliseconds
