Home
last modified time | relevance | path

Searched refs:event (Results 1 – 25 of 69) sorted by relevance

123

/openssl/doc/designs/quic-design/
H A Dqlog.md44 event name.
46 This (category name, event name) tuple is known as the event type.
48 - zero or more macros which log fields inside a qlog event.
74 Each event type can be turned on and off individually.
108 event type). If this symbol is omitted, `+` is assumed.
110 - `+*` (or `*`) enables all event types.
112 - `-*` disables all event types.
116 - `-quic:version_information` disables a specific event type.
122 then the `quic:version_information` event is disabled, then all event types are
123 disabled, then the `quic:packet_sent` event is re-enabled.
[all …]
H A Dquic-fc.md113 ---> event: On TX (numBytes)
115 <--- event: On TX Blocked
138 On TX event and increased by the On TX Window Updated event. In fact, it is
178 ---> event: On RX Controlled Bytes (numBytes) [internal event]
181 <--- event: Flow Control Error
188 controllers. Callers do not pass the event themselves. The event is generated by
223 - The On Retire Controlled Bytes event may optionally pass the same event
227 - An additional event is added, which replaces the On RX Controlled Bytes event:
236 This event is used to generate the internal On RX Controlled Bytes event to
241 event if a previous such event already had an equal or greater value. The
[all …]
H A Dquic-fault-injector.md5 processes them accordingly. It will need to behave appropriately in the event of
12 implementation behaves in the expected manner in the event of such misbehaviour.
163 This API will primarily take the form of a set of event listener callbacks. A
164 test will be able to "listen" for a specific event occurring and be informed about
171 Each listener will be provided with additional data about the specific event.
H A Dquic-fifm.md52 retransmission in the event of loss:
116 the event that they are lost. It facilitates the GCR retransmission strategy.
423 subsystems in the event of a packet being acked, lost or discarded. In
508 In the event of packet loss, ACK or discard, the appropriate QUIC Send Stream,
/openssl/test/recipes/70-test_quic_multistream_data/
H A Dverify-qlog.py81 def check_event(filename, event): argument
82 name = event.get("name")
90 if type(event.get("time")) != int:
93 data = event.get('data')
97 if "qlog_format" in event:
108 check_frame(filename, event, frame)
124 data = event['data']
143 def check_frame(filename, event, frame): argument
149 counts = frame_type_counts[event['name']]
160 for event in objs[1:]:
[all …]
/openssl/doc/man3/
H A DSSL_poll.pod107 description of each of the event types.
155 All of the event types are level triggered and represent a readiness or
166 given event will never be reported in I<revents>.
172 In general, an application should always listen for the event types
180 The following event types are supported:
198 specifying this event type in I<events> does nothing.
205 This event is never raised on objects which are not connections.
212 event is raised on a connection.
214 This event is never raised on objects which are not connections.
244 This event is never raised by a receive-only stream.
[all …]
H A DSSL_get_value_uint.pod156 SSL_get_value() does not cause internal event processing to occur unless the
211 and determines the event handling mode in use:
219 event handling model.
224 =item B<SSL_VALUE_EVENT_HANDLING_MODE_IMPLICIT> (Implicit event handling)
226 If set to this value, the implicit event handling model is used. Under this
227 model, QUIC objects will automatically perform background event processing
233 =item B<SSL_VALUE_EVENT_HANDLING_MODE_EXPLICIT> (Explicit event handling)
235 If set to this value, the explicit event handling model is used. Under this
257 implicit event handling model does not in itself cause implicit event handling
260 handling model will not cause event handling to occur before making that
[all …]
H A DDTLSv1_handle_timeout.pod5 DTLSv1_handle_timeout - handle a pending timeout event for a DTLS or QUIC SSL
30 Returns 1 if there was a pending timeout event and it was handled successfully.
32 Returns 0 if there was no pending timeout event, or if the SSL object is not a
35 Returns -1 if there was a pending timeout event but it could not be handled
H A DSSL_handle_events.pod41 calls to L<SSL_get_event_timeout(3)>; event handling is not performed
43 L<SSL_write(3)>. Note that this is different to QUIC which also performs event
H A DSSL_CTX_set_info_callback.pod48 is called whenever a significant event occurs such as: the state changes,
64 state machine event. This may mean that the callback gets invoked more than once
H A DDTLSv1_get_timeout.pod6 timeout event to be handled
H A DSSL_read.pod97 allows internal network event processing to be performed. It is important that
112 In the event of a failure call L<SSL_get_error(3)> to find out the reason which
/openssl/doc/man7/
H A Dopenssl-qlog.pod72 determines which event types are to be logged. Each event type can be turned on
85 Enable all supported qlog event types.
89 Disable all qlog event types.
93 Enable all qlog event types, but disable the B<transport:packet_received> event
98 Disable all qlog event types, except for the B<transport:packet_sent> event type.
135 Enables all event types.
139 Disables all event types.
143 Enables all event types in the B<foo> category.
147 Disables all event types in the B<foo> category.
151 Enables a specific event type B<foo:bar>.
[all …]
H A Dossl-guide-tls-client-non-block.pod66 In a nonblocking application you will need work to perform in the event that
72 complete. Ideally it would only do this in the event that the state of the
145 In the event of an error an application should call L<SSL_get_error(3)> to find
209 the event of a non-fatal failure, it waits until a retry of the I/O operation
211 in the previous section). It returns 1 in the event of a non-fatal error
212 (except EOF), 0 in the event of EOF, or -1 if a fatal error occurred.
H A Dossl-guide-quic-client-non-block.pod51 In a nonblocking application you will need work to perform in the event that
57 complete. Ideally it would only do this in the event that something has changed
178 In the event of an error an application should call L<SSL_get_error(3)> to find
263 the event of a non-fatal failure, it waits until a retry of the I/O operation
265 in the previous section). It returns 1 in the event of a non-fatal error
266 (except EOF), 0 in the event of EOF, or -1 if a fatal error occurred.
/openssl/.github/workflows/
H A Dfips-label.yml24 if: ${{ github.event.workflow_run.event == 'pull_request' }}
27 if: ${{ github.event.workflow_run.conclusion == 'success' }}
34 run_id: ${{github.event.workflow_run.id }},
48 if: ${{ github.event.workflow_run.conclusion == 'success' }}
50 if: ${{ github.event.workflow_run.conclusion == 'success' }}
86 if: ${{ github.event.workflow_run.conclusion == 'success' }}
93 run_id: ${{github.event.workflow_run.id }},
107 if: ${{ github.event.workflow_run.conclusion == 'success' }}
109 if: ${{ github.event.workflow_run.conclusion == 'success' }}
H A Dfips-checksums.yml31 repository: ${{ github.event.pull_request.base.repo.full_name }}
32 ref: ${{ github.event.pull_request.base.ref }}
70 run: echo ${{ github.event.number }} > ./artifact/pr_num
93 repository: ${{ github.event.pull_request.base.repo.full_name }}
94 ref: ${{ github.event.pull_request.base.ref }}
114 run: echo ${{ github.event.number }} > ./artifact/pr_num
H A Dstyle-checks.yml13 PR_NUMBER: ${{ github.event.number }}
H A Dprov-compat-label.yml23 if: ${{ contains(github.event.pull_request.labels.*.name,'extended tests') }}
99 if: ${{ contains(github.event.pull_request.labels.*.name,'extended tests') }}
184 if: ${{ contains(github.event.pull_request.labels.*.name,'extended tests') }}
/openssl/crypto/bio/
H A Dbss_dgram.c1775 struct sctp_event event; in BIO_new_dgram_sctp() local
1849 memset(&event, 0, sizeof(event)); in BIO_new_dgram_sctp()
1850 event.se_assoc_id = 0; in BIO_new_dgram_sctp()
1852 event.se_on = 1; in BIO_new_dgram_sctp()
2034 memset(&event, 0, sizeof(event)); in dgram_sctp_read()
2569 struct sctp_event event; in dgram_sctp_wait_for_dry() local
2578 memset(&event, 0, sizeof(event)); in dgram_sctp_wait_for_dry()
2579 event.se_assoc_id = 0; in dgram_sctp_wait_for_dry()
2581 event.se_on = 1; in dgram_sctp_wait_for_dry()
2648 memset(&event, 0, sizeof(event)); in dgram_sctp_wait_for_dry()
[all …]
/openssl/ssl/quic/
H A Dqlog.c612 const char *event, size_t event_l, in filter_match_event() argument
620 || (event != NULL && event_l != expect_event_l) in filter_match_event()
622 || (event != NULL && memcmp(event, expect_event, expect_event_l))) in filter_match_event()
638 const char *event, size_t event_l) in filter_apply() argument
642 if (filter_match_event(cat, cat_l, event, event_l, \ in filter_apply()
684 const char *cat, *event; in ossl_qlog_set_filter() local
717 lex_get_rest(&lex, &event, &event_l); in ossl_qlog_set_filter()
720 if (!validate_name(&event, &event_l)) in ossl_qlog_set_filter()
723 filter_apply(enabled, add, cat, cat_l, event, event_l); in ossl_qlog_set_filter()
/openssl/providers/fips/
H A Dself_test.h34 int SELF_TEST_kats(OSSL_SELF_TEST *event, OSSL_LIB_CTX *libctx);
/openssl/doc/designs/ddd/
H A DREPORT.md83 - Additional functions in application code to determine event handling
85 the QUIC event loop (`pump`).
113 - The API to expose the event handling deadline for the QUIC engine
118 - The API to perform QUIC event processing has been renamed to be
137 internal assist thread is used to perform QUIC event handling, enables an
209 - Additional functions in application code to determine event handling
211 the QUIC event loop (`pump`).
289 - Additional use of libuv to configure a timer event;
/openssl/ssl/statem/
H A DREADME.md22 event of NBIO events; handling the common flow of steps for reading a
/openssl/doc/internal/man3/
H A Dossl_init_thread_deregister.pod43 In the event that previously registered stop handlers need to be deregistered

Completed in 55 milliseconds

123