| /openssl-master/Configurations/ |
| A D | common0.tmpl | 3 # Commonly used list of generated files
9 # filter out all that are not generated
12 ( # The sources of stuff may be generated
19 # Things we explicitly depend on are usually generated
22 our @generated =
25 # Scripts are assumed to be generated, so add them too
|
| /openssl-master/test/ |
| A D | rdrand_sanitytest.c | 32 size_t generated = 0; in sanity_check_bytes() local
36 generated = rng(buf, sizeof(buf)); in sanity_check_bytes()
37 if (generated == sizeof(buf)) in sanity_check_bytes()
54 if (!TEST_int_eq(generated, sizeof(buf))) in sanity_check_bytes()
|
| /openssl-master/test/recipes/30-test_evp_data/ |
| A D | evpciph_rc5.txt | 9 #The following tests were generated using legacy code, to ensure that the
25 #Self generated. Bigger key.
48 #Self generated. Bigger key.
73 #Self generated. Bigger key.
|
| A D | evppkey_sm2.txt | 56 # Test with an C1y value < 32 bytes in length (self generated)
62 # Test with an C1x and C1y valuey > 32 bytes in length, and longer plaintext (self generated)
70 # anything about the generated signature being valid, nor does it test the
|
| /openssl-master/ |
| A D | HACKING.md | 30 If a merge error occurs in one of these generated files then the
31 generated files need to be removed and regenerated using `make update`.
32 To aid in this process the generated files can be committed separately
|
| /openssl-master/doc/man1/ |
| A D | openssl-dhparam.pod.in | 80 input file is ignored and parameters are generated instead. If not
81 present but I<numbits> is present, parameters are generated with the
86 This option specifies that a parameter set should be generated of size
88 the input file is ignored and parameters are generated instead. If
90 present, parameters are generated with a default length of 2048 bits.
|
| A D | openssl-gendsa.pod.in | 34 (which will be typically generated by the L<openssl-dsaparam(1)> command).
71 the size of the private key. DSA parameters can be generated and
|
| A D | openssl-dsaparam.pod.in | 74 This option will generate a DSA either using the specified or generated
88 This option specifies that a parameter set should be generated of size
|
| /openssl-master/doc/man3/ |
| A D | EVP_PKEY_encapsulate.pod | 26 I<*outlen> parameter and the maximum size of the generated key buffer is written
28 internally generated key is written to I<genkey> and its size is written to
29 I<*genkeylen>. The encapsulated version of the generated key is written to
76 * The generated 'secret' can be used as key material.
|
| A D | DSA_generate_parameters.pod | 37 B<bits> is the length of the prime p to be generated.
41 If B<seed> is NULL, the primes will be generated at random.
62 When a candidate for q is generated, B<BN_GENCB_call(cb, 0, m++)> is called
81 Before a candidate for p (other than the first) is generated and tested,
|
| A D | DH_generate_parameters.pod | 46 The parameters generated by DH_generate_parameters_ex() should not be used in
49 B<prime_len> is the length in bits of the safe prime to be generated.
55 number is generated, and when a prime has been found, B<BN_GENCB_call(cb, 3, 0)>
|
| A D | SSL_CTX_set_stateless_cookie_generate_cb.pod | 46 of bytes written to B<cookie_len>. If a cookie cannot be generated, a zero
62 cookie cannot be generated, a zero return value can be used to abort the
|
| A D | SSL_CTX_set_session_id_context.pod | 26 Sessions are generated within a certain context. When exporting/importing
28 to re-import a session generated from another context (e.g. another
|
| /openssl-master/fuzz/ |
| A D | README.md | 101 the fuzz/*-test binaries and the file generated by the fuzzer. They binaries
107 reproduce the generated random numbers.
140 The coverage depends on the way the numbers are generated. We don't disable any
142 numbers that were generated. For instance the client fuzzer will always generate
144 emulated by the file, can be generated for that client hello.
156 The client and server corpus is generated with multiple config options:
|
| /openssl-master/doc/man7/ |
| A D | EVP_PKEY-RSA.pod | 120 The value should be the number of primes for the generated B<RSA> key. The
123 being generated so the maximum number could be less.
146 These 2 fields are normally randomly generated and are used to generate "p" and
157 These 4 fields are normally randomly generated. The prime factors "p1", "p2",
205 An B<RSA> key can be generated simply like this:
219 An B<RSA> key can be generated with key generation parameters:
|
| A D | EVP_KEYEXCH-DH.pod | 41 To convert the peer's generated key pair to a public key in DER format in order
44 EVP_PKEY *peer_key; /* It is assumed this contains the peers generated key */
90 using the host's public key and the peer's generated key pair.
|
| A D | provider-kem.pod | 108 The parameter I<provctx> is the provider context generated during provider
126 The key object should have been previously generated, loaded or imported into
133 Unless I<out> is NULL, the data to be encapsulated is internally generated,
137 I<*outlen> and the length of the generated secret should be written to
141 written to I<*outlen>, and the maximum length of the generated secret should be
150 The key object should have been previously generated, loaded or imported into
|
| A D | EVP_PKEY-DH.pod | 79 Randomly generated safe primes are not allowed by FIPS, so setting this value
129 An optional value to set the maximum length of the generated private key.
143 A B<DH> key can be generated with a named safe prime group by calling:
162 B<DHX> domain parameters can be generated according to B<FIPS 186-4> by calling:
189 A B<DH> key can be generated using domain parameters by calling:
|
| A D | EVP_PKEY-DSA.pod | 38 The B<DSA> domain parameters can be generated by calling:
62 A B<DSA> key can be generated using domain parameters by calling:
|
| A D | EVP_PKEY-X25519.pod | 85 An B<X25519> key can be generated like this:
89 An B<X448>, B<ED25519>, or B<ED448> key can be generated likewise.
|
| A D | EVP_PKEY-SM2.pod | 38 B<SM2> signatures can be generated by using the 'DigestSign' series of APIs, for
58 Since version 3.0, SM2 keys can be generated and loaded only when the domain
|
| /openssl-master/test/recipes/04-test_pem_reading_data/ |
| A D | NOTES.txt | 1 The cert-*.pem and dsa-*.pem files are generated as manipulation of the
|
| /openssl-master/doc/HOWTO/ |
| A D | keys.txt | 10 generated separately.
50 question (actually, several keys can be generated from the same
66 the key will be generated:
|
| /openssl-master/external/perl/Text-Template-1.56/ |
| A D | MANIFEST | 1 # This file was automatically generated by Dist::Zilla::Plugin::Manifest v6.012.
|
| /openssl-master/providers/common/der/ |
| A D | DSA.asn1 | 10 -- OID for DSA signature generated with SHA-1 hash
|