/openssl/crypto/asn1/ |
H A D | a_d2i_fp.c | 114 size_t want = HEADER_SIZE; in asn1_d2i_read_bio() local 133 if (want >= diff) { in asn1_d2i_read_bio() 134 want -= diff; in asn1_d2i_read_bio() 136 if (len + want < len || !BUF_MEM_grow_clean(b, len + want)) { in asn1_d2i_read_bio() 179 want = HEADER_SIZE; in asn1_d2i_read_bio() 186 want = HEADER_SIZE; in asn1_d2i_read_bio() 189 want = slen; in asn1_d2i_read_bio() 199 while (want > 0) { in asn1_d2i_read_bio() 206 size_t chunk = want > chunk_max ? chunk_max : want; in asn1_d2i_read_bio() 212 want -= chunk; in asn1_d2i_read_bio() [all …]
|
/openssl/test/helpers/ |
H A D | ssltestlib.h | 21 int create_bare_ssl_connection(SSL *serverssl, SSL *clientssl, int want, 26 int create_ssl_connection(SSL *serverssl, SSL *clientssl, int want);
|
H A D | ssltestlib.c | 1057 int create_bare_ssl_connection(SSL *serverssl, SSL *clientssl, int want, in create_bare_ssl_connection() argument 1092 if (want != SSL_ERROR_SSL) in create_bare_ssl_connection() 1096 if (want != SSL_ERROR_NONE && err == want) in create_bare_ssl_connection() 1126 if (want != SSL_ERROR_SSL) in create_bare_ssl_connection() 1130 if (want != SSL_ERROR_NONE && err == want) in create_bare_ssl_connection() 1179 int create_ssl_connection(SSL *serverssl, SSL *clientssl, int want) in create_ssl_connection() argument 1185 if (!create_bare_ssl_connection(serverssl, clientssl, want, 1, 0)) in create_ssl_connection()
|
/openssl/test/ |
H A D | danetest.c | 303 int want; in test_tlsafile() local 316 &ntlsa, &ncert, &noncheck, &want, &want_depth, &off) != 5 in test_tlsafile() 360 if (!TEST_int_eq(err, want)) { in test_tlsafile() 361 if (want == X509_V_OK) in test_tlsafile() 369 if (!TEST_false(want == 0 && ok == 0)) { in test_tlsafile()
|
H A D | README.md | 21 You may want increased verbosity, that can be accomplished like this: 40 If you want to run just one or a few specific tests, you can use 103 or, if you want to be explicit:
|
H A D | README-dev.md | 7 For any test that you want to perform, you write a script located in 103 to modify the include paths and source files if you don't want to use the
|
/openssl/doc/designs/quic-design/ |
H A D | quic-requirements.md | 126 interactions. We want to be able to enable them to transfer to using single 130 interactions. We want to be able to enable them to transfer to using single 131 stream QUIC easily. More likely to want to do multi-stream. 136 using fibres). Would prefer to use the existing APIs - they don’t want to throw 150 applications should be able to pick whatever protocol they want to use 164 * The internal architecture should allow for the fact that we may want to 201 interactions. We want to be able to enable them to transfer to using single
|
H A D | dgram-api.md | 220 msghdr`, *m\*v* iovecs, etc. Since we want to support multithreaded use 259 it later. So we might want to start with something small, like 8. 303 The problem here is we want to support “single-copy” (where the data is only 372 like setters and getters of the same variables from the name.) We probably want 385 We probably want this for our own QUIC implementation built on top of this 388 want use `sendmmsg` constructively in trivial cases (e.g. where we send two 445 But since this seems a very strange API usage pattern, we may just want to fail 463 It is a functional assumption of the above design that we would never want to 467 If we did ever want to do this, multiple BIOs on the same FD is one possibility 481 fill. We might want to have a way to specify how many buffers it should offer to
|
/openssl/doc/HOWTO/ |
H A D | certificates.txt | 33 you want a RSA private key, or if you want a DSA private key: 75 You can create a self-signed certificate if you don't want to deal 76 with a certificate authority, or if you just want to create a test
|
H A D | keys.txt | 27 you don't want your key to be protected by a password, remove the flag 56 you don't want your key to be protected by a password, remove the flag 82 If you don't want your key to be protected by a password, remove the flag
|
/openssl/ |
H A D | README-PROVIDERS.md | 34 automatically. Therefore if you want to use it in conjunction with other 81 This can be useful if you are using non-default library contexts and want 115 often also want to explicitly load the default provider, as is done here:
|
H A D | NOTES-WINDOWS.md | 76 - `perl Configure VC-WIN32` if you want 32-bit OpenSSL or 77 - `perl Configure VC-WIN64A` if you want 64-bit OpenSSL or 78 - `perl Configure VC-WIN64-ARM` if you want Windows on Arm (win-arm64) 126 `vcvarsall.bat` before you compile. For example, if you want to build
|
H A D | README-ENGINES.md | 108 switch called "-engine". Also, if you want to use the ENGINE support in 110 select the ENGINE implementation you want. 144 them, if you want them, in the form of "dynamic"-loadable 307 the "-t" switch to the utility if you want it to try and initialise
|
/openssl/test/recipes/30-test_evp_data/ |
H A D | evpmac_sm3.txt | 36 Input = "what do ya want for nothing?"
|
/openssl/Configurations/ |
H A D | common0.tmpl | 6 # build files only want those for a particular build. Therefore, we
|
/openssl/doc/man7/ |
H A D | openssl-core_names.h.pod | 37 algorithms that OpenSSL providers support will want to pay attention
|
/openssl/.github/workflows/ |
H A D | compiler-zoo.yml | 69 # Often, the full range of oldest->newest compilers we want aren't available
|
/openssl/doc/man3/ |
H A D | BIO_f_md.pod | 87 * For BIO_push() we want to append the sink BIO and keep a note of 112 /* Might want to do something with the data here */
|
H A D | BN_num_bytes.pod | 41 of I<significant> bits a little lower. If you want to know the "key
|
H A D | OPENSSL_instrument_bus.pod | 24 zeroed upon invocation (if you want to retrieve actual probe values).
|
H A D | EVP_PKEY_fromdata.pod | 137 /* Do what you want with |pkey| */ 195 /* Do what you want with |pkey| */
|
H A D | X509_EXTENSION_set_object.pod | 61 applications will want to parse or encode and add an extension: they should
|
/openssl/.github/ISSUE_TEMPLATE/ |
H A D | question.md | 15 want to ask them on the openssl-users@openssl.org mailing list.
|
/openssl/doc/internal/man3/ |
H A D | ossl_method_construct.pod | 35 All libcrypto subsystems that want to create their own methods based 81 when the provider doesn't want its dispatch table stored in a longer
|
/openssl/fuzz/ |
H A D | README.md | 136 Since we want to maximize the coverage of the fuzzing corpus, the client and 171 or for any other reason want to minimize the data
|