Searched refs:I (Results 576 – 600 of 603) sorted by relevance
1...<<2122232425
134 Windows) provide a POSIX compatible interface via the I<socket> function, e.g.145 provide the POSIX compatible I<connect> function. For example:493 specified location (in this case I<stderr>).
435 In particular, a private scalar I<k> outside the range I<< 1 <= k < n-1 >> is682 All functions listed below with a I<NAME> have a replacement function I<NAME_ex>
179 C<activate = 1> (note that setting this value to 0 is I<not> sufficient).
146 for the QUIC state machine and potentially perform network I/O.346 network I/O processing as the resources needed to handle the connection are437 network I/O. Also compatible with DTLSv1 and supersedes `DTLSv1_handle_timeout`518 return value of `SSL_want` can only express one I/O direction at a time (read or612 an I/O would-block condition.1178 see the QUIC I/O Architecture design document.1451 `CONNECTION_CLOSE` frame, QUIC requires that we continue to process network I/O
261 | Type | Name | I | H | 0 | 1 | N | C | P …303 | I | Valid in Initial packets|
450 libssl of network I/O readiness.
42 One typical use of BIO pairs is to place TLS/SSL I/O under application control, this
129 in the call and may therefore I<not> be passed to RSA_set0_key(). If
174 However, OpenSSL's behavior as a TLS 1.3 server is to consider I<all>
28 A memory BIO is a source/sink BIO which uses memory for its I/O. Data
414 renegotiation is referred to as I<patched>. A server not supporting secure415 renegotiation is referred to as I<unpatched>.
38 all datagram network I/O requested by libssl under application control.
94 the data generated I<without> the NUL terminator is returned from the function.
48 function on the B<SSL> object set in the I<x509_store_ctx> ex data (see
126 The terms extract and expand are used by HKDF so I think this name would be
1398 #define I r21 macro1448 mov I=r36 };;1524 { .mii; shr.u r9=H,I // remainder if anybody wants it
31 ! stack wiping I return pointer to the top of stack of the *caller*.
68 debugging and extending the library. They are I<not> to be used by
240 How do I build a "dynamic" ENGINE?
11280 * Handle non-blocking I/O properly in SSL_shutdown() call.12348 internally to the implementation so I've used that for now.13389 * Various fixes to base64 BIO and non blocking I/O. On write15417 I don't think anyone really wanted that behaviour.15936 when using non-blocking I/O.15985 invocations of ssl3_accept when using non-blocking I/O, the16312 half from which PRNG output bytes were taken -- I had always17155 libraries through configuration. I've kept it so the17485 reader "classes" (I can definitely see something reading a19943 is horrible: I feel ill....[all …]
1251 be used instead of -I (or what corresponds1947 I) On operating systems which provide a suitable randomness source (in
726 /* Streaming I/O boundary */
118 # define BIO_CTRL_DGRAM_GET_SEND_TIMER_EXP 38/* I/O operation timed out */
1528 2ocyWASM0WB+DcR4l1PisfY7Mv8BTsQs1qafrIHf5tDW/Urzcq4nxG+I3020 I/UXsVjZiBhB0lce+61j+Fy+LlgZYMXWcGAaZ2AnJnWlSJliF+SrK4684x1x/KY/3237 U+FXP/YL4VB0Z9Qx+7I=3609 MIHuAgEAMBAGByqGSM49AgEGBSuBBAAjBIHWMIHTAgEBBEIBDJCMrxvnTGFrYl/I3885 kLn0C+I=4848 REu/I+DIACIFXvgh3zMEL7gxbdrXZIXb0lkOL1SYqRTk8K0510376 MIHCAgEAMBAGByqGSM49AgEGBSuBBAAlBIGqMIGnAgEBBDQAZxJewwmrXcfqVo+I10445 5wGzNVIa7DBfMU1/I+0ozAxNI/M6Z4X8bG3pPl+rzicTAvlVf20q53xScg7aWi4V10452 t2F9kroQYDzcyoNlVNAkLds31eFXawvmnw7s5wGzNVIa7DBfMU1/I+0ozAxNI/M6
345 MDoCAQAwEwYHKoZIzj0CAQYIKoZIzj0DAAoEIDAeAgEBBBkAY1GZLynO/IDWwOOjEWUE7k+I/MkP1387 MD8CAQAwEwYHKoZIzj0CAQYIKoZIzj0DAQQEJTAjAgEBBB5nH2mt/GUx+I/60NlcuQlrdupDXwMY4261 vuu4aApQiWE3yQd9v/I=
Completed in 184 milliseconds
