Home
last modified time | relevance | path

Searched refs:on (Results 1 – 25 of 793) sorted by relevance

12345678910>>...32

/openssl/crypto/bio/
H A Dbio_sock2.c83 const int on = 1; in BIO_connect() local
95 (const void *)&on, sizeof(on)) != 0) { in BIO_connect()
105 (const void *)&on, sizeof(on)) != 0) { in BIO_connect()
163 (const void *)&on, sizeof(on)) != 0) { in BIO_connect()
215 int on = 1; in BIO_bind() local
230 (const void *)&on, sizeof(on)) != 0) { in BIO_bind()
289 int on = 1; in BIO_listen() local
312 (const void *)&on, sizeof(on)) != 0) { in BIO_listen()
322 (const void *)&on, sizeof(on)) != 0) { in BIO_listen()
337 on = options & BIO_SOCK_V6_ONLY ? 1 : 0; in BIO_listen()
[all …]
/openssl/
H A DNOTES-PERL.md1 Notes on Perl
5 - [Perl on Windows](#perl-on-windows)
6 - [Perl on VMS](#perl-on-vms)
7 - [Perl on NonStop](#perl-on-nonstop)
9 - [Notes on installing a Perl module](#notes-on-installing-a-perl-module])
14 For our scripts, we rely quite a bit on Perl, and increasingly on
23 - on Linux distributions based on Debian, the package `perl` will
25 - on Linux distributions based on RPMs, you will need to install
32 Perl on Windows
46 Perl on VMS
[all …]
H A DNOTES-WINDOWS.md16 Microsoft Visual C++ (MSVC) C compiler on the command line
21 run on the GNU-like development environment MSYS2
22 or run on Linux or Cygwin
24 "Hosted" OpenSSL relies on an external POSIX compatibility layer
63 3. Make sure both Perl and NASM are on your %PATH%
85 on the Universal CRT or
87 on the Universal CRT or
130 A summary table of behavior on Windows platforms
194 These compilers must be on your MSYS2 $PATH.
195 A common error is to not have these on your $PATH.
[all …]
H A DINSTALL.md41 - [Notes on multi-threading](#notes-on-multi-threading)
42 - [Notes on shared libraries](#notes-on-shared-libraries)
43 - [Notes on random number generation](#notes-on-random-number-generation)
44 - [Notes on assembler modules compilation](#notes-on-assembler-modules-compilation)
223 depending on the file type, as it is custom on Unix-like operating systems.
325 building on.
510 Use the `RDSEED` or `RDRAND` command on x86 or `RNDRRS` command on aarch64
975 See [Notes on shared libraries](#notes-on-shared-libraries) below.
1052 See [Notes on multi-threading](#notes-on-multi-threading) below.
1410 `Configure` creates a build file (`Makefile` on Unix, `makefile` on Windows
[all …]
H A DNOTES-VALGRIND.md1 Notes on Valgrind
7 will focus on memcheck.
17 2. Valgrind installed on the platform
46 This variable controls the processor-specific code on Intel processors.
51 As of valgrind-3.15.0 on Linux/x86_64, instructions up to AVX2 are
56 This variable may need to be set to something different based on the
57 processor and Valgrind version you are running tests on. More information
/openssl/doc/designs/quic-design/
H A Derror-handling.md7 The errors are put on the error stack (rather a queue but error stack is
10 error return value. The `SSL_get_error()` call depends on the stack being
40 entries on the error stack.
52 depending on their effect they are either permanent if they cause the
54 they are left on the error stack of the thread that called SSL_write()
55 or SSL_read() on the stream.
60 Return value of SSL_get_error() on QUIC connections or streams does not
61 depend on the error stack contents.
68 replicated for SSL_read()/SSL_write() calls on other streams.
80 are copied to the thread local error stack. They are always kept on
[all …]
/openssl/test/recipes/30-test_evp_data/
H A Devpkdf_argon2.txt103 # Expected fail on condition violation: m_cost < 8 * lanes
112 # Expected fail on condition violation: m_cost < 2 * syncpoints = 8
120 # Expected fail on condition violation: threads > avail threads
130 # Expected fail on condition violation: lanes >= 1
135 # Expected fail on condition violation: lanes <= 0xFFFFFF
140 # Expected fail on condition violation: threads >= 1
145 # Expected fail on condition violation: threads <= 0xFFFFFF
150 # Expected fail on condition violation: outlen >= 4
155 # Expected fail on condition violation: iter >= 1
160 # Expected fail on condition violation: saltlen > 8
[all …]
/openssl/doc/internal/man3/
H A Dossl_cmp_msg_create.pod83 or "illegal body type" on error.
86 or -1 on error.
90 Returns 1 on success, 0 on error.
97 Returns pointer to created B<OSSL_CMP_MSG> on success, NULL on error.
101 Returns 1 on success, 0 on error.
106 Returns 1 on success, 0 on error.
H A Dossl_cmp_msg_check_update.pod7 - generic checks on a received CMP message, updating the context
22 ossl_cmp_msg_check_update() does all generic checks on the given message B<msg>,
51 The callback should return 1 on acceptance, 0 on rejection, or -1 on error.
52 It should not put an error on the error stack since this could be misleading.
76 ossl_cmp_msg_check_update() returns 1 on success, -1 on error.
/openssl/doc/designs/
H A Dhandling-some-max-defines.md37 #### API calls depending on this:
67 #### API calls depending on this:
78 to not depend on this value but there are many such cases. Avoid adding
79 further APIs depending on this value.
90 #### API calls depending on this:
106 on this value.
117 #### API calls depending on this:
125 APIs depending on this value.
138 #### API calls depending on this:
145 Review and modify the codebase to not depend on and use
[all …]
/openssl/doc/designs/ddd/
H A DWINDOWS.md11 method, but only on fairly new versions of Windows.
13 Traditionally, polling has been done on windows using select(). However, this
14 call works a little differently than on POSIX platforms. Whereas on POSIX
15 platforms select() accepts a bitmask of FDs, on Windows select() accepts a
17 because sockets are NT kernel handles on Windows and thus are not allocated
19 POSIX poll(), making select() a viable option for polling on Windows.
28 interface on top of polling, but it is not really possible to build a
29 polling-like interface on top of IOCPs.
42 so on.
73 Further, a cursory examination of code on GitHub seems to suggest that when
[all …]
/openssl/doc/man3/
H A DSSL_stream_reset.pod22 called on a QUIC stream SSL object, or on a QUIC connection SSL object with a
35 a stream when the information transmitted on the stream no longer matters, for
38 This function cannot be called on a unidirectional stream initiated by the peer,
53 Returns 1 on success and 0 on failure.
55 This function fails if called on a QUIC connection SSL object without a default
56 stream attached, or on a non-QUIC SSL object.
H A DBIO_connect.pod34 BIO_listen() has B<sock> start listening on the address and service
40 BIO_accept_ex() waits for an incoming connections on the given
44 on the accepted socket. The flags are described in L</FLAGS> below.
78 Enables TCP Fast Open on the socket. Uses appropriate APIs on
94 BIO_socket() returns the socket number on success or B<INVALID_SOCKET>
95 (-1) on error. When an error has occurred, the OpenSSL error stack
98 BIO_bind(), BIO_connect() and BIO_listen() return 1 on success or 0 on error.
102 BIO_accept_ex() returns the accepted socket on success or
103 B<INVALID_SOCKET> (-1) on error. When an error has occurred, the
H A DSSL_handle_events.pod15 SSL_handle_events() performs any internal processing which is due on a SSL object. The
16 exact operations performed by SSL_handle_events() vary depending on what kind of protocol
19 possible, to perform network I/O operations on one of the BIOs underlying the
34 Using SSL_handle_events() on an SSL object being used with a DTLS method allows timeout
48 Using SSL_handle_events() on an SSL object which represents a QUIC connection allows
54 need to call SSL_handle_events() because OpenSSL performs ticking internally on an
61 Calling SSL_handle_events() on a QUIC connection SSL object being used in blocking mode
65 SSL_handle_events() may optionally be used on a QUIC connection object if desired.
73 Calling SSL_handle_events() on any other kind of SSL object is a no-op. This is
81 Returns 1 on success and 0 on failure.
H A DEVP_PKEY_ASN1_METHOD.pod167 They MUST return 0 on error, 1 on success.
177 It MUST return 0 on error, 1 on success.
187 They MUST return 0 on error, 1 on success.
192 It MUST return 0 on error, 1 on success.
216 They MUST return 0 on error, 1 on success.
225 It MUST return 0 on error, 1 on success.
235 It MUST return 0 on error, 1 on success.
247 It MUST return 0 on error, 1 on success.
272 old_priv_decode() MUST return 0 on error, 1 on success.
340 It MUST return 0 on error, or 1 on success.
[all …]
H A DBIO_s_accept.pod48 Read and write operations on an accept BIO will perform I/O
49 on the underlying connection. If no connection is established
55 If the close flag is set on an accept BIO then any active
56 connection on that chain is shutdown and the socket closed when
59 Calling BIO_reset() on an accept BIO will close any active
135 accept->socket. This effectively means that attempting I/O on
137 perform I/O on it.
183 BIO_get_peer_name() returns the peer name or NULL on error.
191 BIO_new_accept() returns a BIO or NULL on error.
219 fprintf(stderr, "Sent out data on connection 1\n");
[all …]
H A DX509_STORE_set_verify_cb_func.pod136 The final chain verification functions must return 0 on failure and 1
137 on success.
159 This function must return 0 on failure (among others if I<x> hasn't
160 been issued with I<issuer>) and 1 on success.
168 It must return 0 on failure and 1 on success.
175 This function must return 0 on failure and 1 on success.
181 This function must return 0 on failure and 1 on success.
187 This function must return 0 on failure and 1 on success.
193 This function must return 0 on failure and 1 on success.
200 These functions return NULL on failure and a pointer to a stack of
[all …]
H A DBIO_s_core.pod25 Once a BIO is constructed based on BIO_s_core(), the associated OSSL_CORE_BIO
26 object should be set on it using BIO_set_data(3). Note that the BIO will only
32 based on BIO_s_core() and that is associated with the given library context. It
33 then also sets the OSSL_CORE_BIO object on the BIO using BIO_set_data(3).
39 BIO_new_from_core_bio() returns a BIO structure on success or NULL on failure.
H A DSSL_get_stream_read_state.pod41 This value is returned if called on a non-QUIC SSL object, or on a QUIC
46 This value is returned on a stream which has not been concluded and remains
51 This value is returned if SSL_get_stream_read_state() is called on a
53 SSL_get_stream_write_state() is called on a remotely-initiated (and thus
97 that it does not wish to receive further data on the sending part of the stream.
133 B<SSL_STREAM_STATE> values. If called on a non-QUIC SSL object, or a QUIC
138 on success and 0 if the stream was terminated normally. They return -1 on error,
140 connection closure, if called on a stream for which the respective stream part
141 does not exist (e.g. on a unidirectional stream), or if called on a non-QUIC
H A DSSL_CTX_set1_cert_comp_preference.pod67 the configured certificates on an SSL_CTX/SSL object with algorithm B<alg>. If
69 in the preference list. Calling these functions on a client SSL_CTX/SSL object
74 use. Calling these functions on a client SSL_CTX/SSL object will result in an
95 on a client SSL_CTX/SSL object will return an error. Client certificates are
96 compressed on-demand as unique context data from the server is compressed along
103 SSL_get1_compressed_cert() is the last certificate set on the SSL_CTX/SSL object.
123 Sending compressed certificates may be disabled on a connection via the
125 may be disabled on a connection via the SSL_OP_NO_RX_CERTIFICATE_COMPRESSION
136 return 1 for success and 0 on error.
140 return the length of the allocated memory on success and 0 on error.
H A DSSL_set_default_stream_mode.pod24 made on a QUIC connection SSL object are redirected. Default stream handling
28 When not disabled, a default stream is automatically created on an outgoing
48 functions which require a stream on the QUIC connection SSL object (for example,
51 It is recommended that new applications and applications which rely on multiple
56 handling. It can only be called on a QUIC connection SSL object prior to any
87 L<SSL_read(3)> and L<SSL_write(3)> calls cannot be made on the QUIC connection
93 A default stream will not be automatically created on a QUIC connection SSL
101 SSL_set_default_stream_mode() returns 1 on success and 0 on failure.
106 These functions fail if called on a QUIC stream SSL object or on a non-QUIC SSL
H A DSSL_stream_conclude.pod16 part of a QUIC stream. If called on a QUIC connection SSL object with an
26 When calling this on a stream, the receive part of the stream remains
35 This function is not supported on an object other than a QUIC stream SSL object.
39 Returns 1 on success and 0 on failure.
41 Returns 0 if called on an SSL object not representing a QUIC stream.
H A DSSL_SESSION_free.pod27 SSL_SESSION_up_ref() increments the reference count on the given SSL_SESSION
38 is successfully completed. Depending on the settings, see
57 It must not be called on other SSL_SESSION objects, as this would cause
63 or NULL on error.
65 SSL_SESSION_dup returns a pointer to the new copy or NULL on error.
67 SSL_SESSION_up_ref returns 1 on success or 0 on error.
/openssl/crypto/objects/
H A Do_names.c153 OBJ_NAME on, *ret; in OBJ_NAME_get() local
167 on.name = name; in OBJ_NAME_get()
168 on.type = type; in OBJ_NAME_get()
171 ret = lh_OBJ_NAME_retrieve(names_lh, &on); in OBJ_NAME_get()
177 on.name = ret->data; in OBJ_NAME_get()
244 OBJ_NAME on, *ret; in OBJ_NAME_remove() local
254 on.name = name; in OBJ_NAME_remove()
255 on.type = type; in OBJ_NAME_remove()
256 ret = lh_OBJ_NAME_delete(names_lh, &on); in OBJ_NAME_remove()
/openssl/test/ssl-tests/
H A D09-alpn.cnf8 test-3 = 3-alpn-alert-on-mismatch
118 [3-alpn-alert-on-mismatch]
119 ssl_conf = 3-alpn-alert-on-mismatch-ssl
121 [3-alpn-alert-on-mismatch-ssl]
122 server = 3-alpn-alert-on-mismatch-server
123 client = 3-alpn-alert-on-mismatch-client
125 [3-alpn-alert-on-mismatch-server]
130 [3-alpn-alert-on-mismatch-client]
141 [3-alpn-alert-on-mismatch-server-extra]
144 [3-alpn-alert-on-mismatch-client-extra]
[all …]

Completed in 50 milliseconds

12345678910>>...32