Lines Matching full:semantics
90 | Semantics | API | Status |
131 - **Semantics**: This can be one of:
133 - **Unchanged**: The semantics of this existing libssl API call are
135 - **Changed**: The semantics are changed for QUIC.
171 | Semantics | `SSL_get_error` | Can Tick? | CSHL |
177 | Semantics | `SSL_get_error` | Can Tick? | CSHL |
182 we do not implement server support at this time. However, the semantics of this
187 | Semantics | `SSL_get_error` | Can Tick? | CSHL |
193 | Semantics | `SSL_get_error` | Can Tick? | CSHL |
201 | Semantics | `SSL_get_error` | Can Tick? | CSHL |
209 | Semantics | `SSL_get_error` | Can Tick? | CSHL |
220 | Semantics | `SSL_get_error` | Can Tick? | CSHL |
239 | Semantics | `SSL_get_error` | Can Tick? | CSHL |
259 | Semantics | `SSL_get_error` | Can Tick? | CSHL |
265 | Semantics | `SSL_get_error` | Can Tick? | CSHL |
271 - Semantics unchanged or approximated (essentially, `SSL_pending() || any RXE
273 - Change semantics to only determine the return value based on if there is
278 | Semantics | `SSL_get_error` | Can Tick? | CSHL |
289 | Semantics | `SSL_get_error` | Can Tick? | CSHL |
305 - Preserve `SSL_clear` semantics at the handshake layer, reset all QUIC state
308 **TBD:** Semantics of this on stream objects.
312 | Semantics | `SSL_get_error` | Can Tick? | CSHL |
363 | Semantics | `SSL_get_error` | Can Tick? | CSHL |
369 The changes to the semantics of these calls are as follows:
371 - The BIO MUST be a BIO with datagram semantics (this is a change relative to
379 | Semantics | `SSL_get_error` | Can Tick? | CSHL |
395 | Semantics | `SSL_get_error` | Can Tick? | CSHL |
403 | Semantics | `SSL_get_error` | Can Tick? | CSHL |
432 | Semantics | `SSL_get_error` | Can Tick? | CSHL |
442 | Semantics | `SSL_get_error` | Can Tick? | CSHL |
462 | Semantics | `SSL_get_error` | Can Tick? | CSHL |
469 is no longer viable, thus blocking semantics at the application level must be
479 | Semantics | `SSL_get_error` | Can Tick? | CSHL |
496 | Semantics | `SSL_get_error` | Can Tick? | CSHL |
525 | Semantics | `SSL_get_error` | Can Tick? | CSHL |
540 | Semantics | `SSL_get_error` | Can Tick? | CSHL |
622 state semantics if the application happens to call `SSL_handle_events`, until it
645 | Semantics | `SSL_get_error` | Can Tick? | CSHL |
681 | Semantics | `SSL_get_error` | Can Tick? | CSHL |
716 | Semantics | `SSL_get_error` | Can Tick? | CSHL |
803 | Semantics | `SSL_get_error` | Can Tick? | CSHL |
829 | Semantics | `SSL_get_error` | Can Tick? | CSHL |
910 | Semantics | `SSL_get_error` | Can Tick? | CSHL |
929 | Semantics | `SSL_get_error` | Can Tick? | CSHL |
946 | Semantics | `SSL_get_error` | Can Tick? | CSHL |
970 | Semantics | `SSL_get_error` | Can Tick? | CSHL |
988 | Semantics | `SSL_get_error` | Can Tick? | CSHL |
1003 | Semantics | `SSL_get_error` | Can Tick? | CSHL |
1031 | Semantics | `SSL_get_error` | Can Tick? | CSHL |
1070 | Semantics | `SSL_get_error` | Can Tick? | CSHL |
1088 | Semantics | `SSL_get_error` | Can Tick? | CSHL |
1120 | Semantics | `SSL_get_error` | Can Tick? | CSHL |
1196 with datagram semantics.
1201 `BIO_f_buffer`. This is problematic because the datagram semantics of writes are
1272 a boolean value which may be implemented by BIOs with datagram semantics. When
1355 the existing BIO pair but provides datagram semantics. It provides full support
1398 This is a basic memory buffer BIO with datagram semantics. Unlike
1438 semantics of `SSL_write` are preserved unchanged.