| /freebsd/sys/contrib/libsodium/src/libsodium/randombytes/ |
| H A D | randombytes.c | 30 static const randombytes_implementation *implementation; variable
47 if (implementation == NULL) { in randombytes_init_if_needed()
48 implementation = RANDOMBYTES_DEFAULT_IMPLEMENTATION; in randombytes_init_if_needed()
56 implementation = impl; in randombytes_set_implementation()
66 return implementation->implementation_name(); in randombytes_implementation_name()
77 return implementation->random(); in randombytes_random()
90 if (implementation->stir != NULL) { in randombytes_stir()
91 implementation->stir(); in randombytes_stir()
132 if (implementation->uniform != NULL) { in randombytes_uniform()
133 return implementation->uniform(upper_bound); in randombytes_uniform()
[all …]
|
| /freebsd/sys/contrib/libsodium/src/libsodium/crypto_stream/salsa20/ |
| H A D | stream_salsa20.c | 22 static const crypto_stream_salsa20_implementation *implementation = variable
25 static const crypto_stream_salsa20_implementation *implementation = variable
51 return implementation->stream(c, clen, n, k); in crypto_stream_salsa20()
60 return implementation->stream_xor_ic(c, m, mlen, n, ic, k); in crypto_stream_salsa20_xor_ic()
68 return implementation->stream_xor_ic(c, m, mlen, n, 0U, k); in crypto_stream_salsa20_xor()
81 implementation = &crypto_stream_salsa20_xmm6_implementation; in _crypto_stream_salsa20_pick_best_implementation()
83 implementation = &crypto_stream_salsa20_ref_implementation; in _crypto_stream_salsa20_pick_best_implementation()
89 implementation = &crypto_stream_salsa20_xmm6int_avx2_implementation; in _crypto_stream_salsa20_pick_best_implementation()
95 implementation = &crypto_stream_salsa20_xmm6int_sse2_implementation; in _crypto_stream_salsa20_pick_best_implementation()
|
| /freebsd/sys/contrib/libsodium/src/libsodium/crypto_stream/chacha20/ |
| H A D | stream_chacha20.c | 17 static const crypto_stream_chacha20_implementation *implementation = variable
56 return implementation->stream(c, clen, n, k); in crypto_stream_chacha20()
63 return implementation->stream_ietf(c, clen, n, k); in crypto_stream_chacha20_ietf()
72 return implementation->stream_xor_ic(c, m, mlen, n, ic, k); in crypto_stream_chacha20_xor_ic()
81 return implementation->stream_ietf_xor_ic(c, m, mlen, n, ic, k); in crypto_stream_chacha20_ietf_xor_ic()
89 return implementation->stream_xor_ic(c, m, mlen, n, 0U, k); in crypto_stream_chacha20_xor()
97 return implementation->stream_ietf_xor_ic(c, m, mlen, n, 0U, k); in crypto_stream_chacha20_ietf_xor()
115 implementation = &crypto_stream_chacha20_ref_implementation; in _crypto_stream_chacha20_pick_best_implementation()
119 implementation = &crypto_stream_chacha20_dolbeau_avx2_implementation; in _crypto_stream_chacha20_pick_best_implementation()
125 implementation = &crypto_stream_chacha20_dolbeau_ssse3_implementation; in _crypto_stream_chacha20_pick_best_implementation()
|
| /freebsd/sys/contrib/libsodium/src/libsodium/crypto_onetimeauth/poly1305/ |
| H A D | onetimeauth_poly1305.c | 14 static const crypto_onetimeauth_poly1305_implementation *implementation = variable
21 return implementation->onetimeauth(out, in, inlen, k); in crypto_onetimeauth_poly1305()
30 return implementation->onetimeauth_verify(h, in, inlen, k); in crypto_onetimeauth_poly1305_verify()
37 return implementation->onetimeauth_init(state, key); in crypto_onetimeauth_poly1305_init()
45 return implementation->onetimeauth_update(state, in, inlen); in crypto_onetimeauth_poly1305_update()
52 return implementation->onetimeauth_final(state, out); in crypto_onetimeauth_poly1305_final()
83 implementation = &crypto_onetimeauth_poly1305_donna_implementation; in _crypto_onetimeauth_poly1305_pick_best_implementation()
86 implementation = &crypto_onetimeauth_poly1305_sse2_implementation; in _crypto_onetimeauth_poly1305_pick_best_implementation()
|
| /freebsd/sys/contrib/libsodium/src/libsodium/crypto_scalarmult/curve25519/ |
| H A D | scalarmult_curve25519.c | 11 static const crypto_scalarmult_curve25519_implementation *implementation = variable
21 if (implementation->mult(q, n, p) != 0) { in crypto_scalarmult_curve25519()
33 return implementation->mult_base(q, n); in crypto_scalarmult_curve25519_base()
51 implementation = &crypto_scalarmult_curve25519_ref10_implementation; in _crypto_scalarmult_curve25519_pick_best_implementation()
55 implementation = &crypto_scalarmult_curve25519_sandy2x_implementation; in _crypto_scalarmult_curve25519_pick_best_implementation()
|
| /freebsd/usr.bin/sed/ |
| H A D | POSIX | 39 backslash in front of it. This implementation follows the BSD
48 implementation permits whitespace but does not require it.
52 POSIX. This implementation permits whitespace but does not
59 is a cleanup, and is followed by this implementation.
76 one might reverse the behaviour.) This implementation follows
84 command. This implementation follows historic practice and
97 This implementation follows historic practice.
105 any particular purpose, this implementation follows the POSIX
122 However, the current practice adopted by this implementation,
131 does not specify this. This implementation follows historical
[all …]
|
| /freebsd/crypto/openssl/doc/man7/ |
| H A D | provider-encoder.pod | 59 The ENCODER implementation may be part of a chain, where data is
61 implementation to encode an object to DER (that object is assumed to
126 The name of an implementation should match the type of object it handles.
127 For example, an implementation that encodes an RSA key should be named "RSA".
128 Likewise, an implementation that further encodes DER should be named "DER".
130 Properties can be used to further specify details about an implementation:
136 This property is used to specify what type of output the implementation
147 An implementation with that output type outputs human readable text, making
148 that implementation suitable for C<-text> output in diverse L<openssl(1)>
153 An implementation with that output type outputs PEM formatted data.
[all …]
|
| H A D | EVP_MD-SHA1.pod | 5 EVP_MD-SHA1 - The SHA1 EVP_MD implementation
13 This implementation is available with the FIPS provider as well as the
18 This implementation supports the common gettable parameters described
23 This implementation supports the following L<OSSL_PARAM(3)> entries,
35 The digest implementation should calculate the complete digest as per RFC6101
|
| H A D | EVP_MD-MD5-SHA1.pod | 5 EVP_MD-MD5-SHA1 - The MD5-SHA1 EVP_MD implementation
15 This implementation is only available with the default provider, and is
20 This implementation supports the common gettable parameters described
25 This implementation supports the following L<OSSL_PARAM(3)> entries,
37 The digest implementation should calculate the complete digest as per RFC6101
|
| H A D | provider-decoder.pod | 59 The DECODER implementation may be part of a chain, where data is
61 implementation to decode an object from PEM to DER, and another one
108 The name of an implementation should match the target type of object
109 it decodes. For example, an implementation that decodes an RSA key
110 should be named "RSA". Likewise, an implementation that decodes DER data
113 Properties can be used to further specify details about an implementation:
119 This property is used to specify what format of input the implementation
130 An implementation with that input type decodes PEM formatted data.
134 An implementation with that input type decodes DER formatted data.
138 An implementation with that input type decodes MSBLOB formatted data.
[all …]
|
| H A D | EVP_MD-MDC2.pod | 5 EVP_MD-MDC2 - The MDC2 EVP_MD implementation
13 This implementation is only available with the legacy provider, and is
18 This implementation supports the common gettable parameters described
23 This implementation supports the following L<OSSL_PARAM(3)> entries,
|
| H A D | EVP_MAC-Poly1305.pod | 5 EVP_MAC-Poly1305 - The Poly1305 EVP_MAC implementation
13 This implementation is identified with this name and properties, to be
54 The OpenSSL implementation of the Poly 1305 MAC corresponds to RFC 7539.
57 RFC 8439 applies equally to the OpenSSL implementation.
|
| H A D | crypto.pod | 29 a "default" implementation suitable for general use, and a "fips" implementation
49 provider loaded that contains an implementation of it. OpenSSL comes with a
102 In order to use an algorithm an implementation for it must first be "fetched".
105 the implementation that will be used.
130 implementation. Instead, the diverse OpenSSL APIs often have explicit fetching
134 be used to explicitly fetch a digest algorithm implementation. The user is
159 implementation.
163 The algorithm implementation that is fetched can then be used with other diverse
171 associated implementation, such as L<EVP_sha256(3)>, L<EVP_aes_128_cbc(3)>,
177 L<EVP_CipherInit_ex(3)>, the actual implementation to be used is
[all …]
|
| H A D | provider-object.pod | 57 implementation where the object originated (let's call it X) and its target
58 implementation (let's call it Y):
64 I<An object loading function in the target implementation>
66 The target implementation (Y) may have a function that can take an I<object
67 reference>. This can only be used if the target implementation is from the
70 The exact target implementation to use is determined from the I<object type>
79 I<An object exporter in the originating implementation>
81 The originating implementation (X) may have an exporter function. This
83 that can then be imported by the target implementation's imported function.
85 This can be used when it's not possible to fetch the target implementation
|
| H A D | EVP_MD-MD4.pod | 5 EVP_MD-MD4 - The MD4 EVP_MD implementation
13 This implementation is only available with the legacy provider, and is
18 This implementation supports the common gettable parameters described
|
| H A D | EVP_MD-MD2.pod | 5 EVP_MD-MD2 - The MD2 EVP_MD implementation
13 This implementation is only available with the legacy provider, and is
18 This implementation supports the common gettable parameters described
|
| H A D | EVP_MD-MD5.pod | 5 EVP_MD-MD5 - The MD5 EVP_MD implementation
13 This implementation is only available with the default provider, and is
18 This implementation supports the common gettable parameters described
|
| H A D | EVP_MD-WHIRLPOOL.pod | 5 EVP_MD-WHIRLPOOL - The WHIRLPOOL EVP_MD implementation
13 This implementation is only available with the legacy provider, and is
18 This implementation supports the common gettable parameters described
|
| H A D | EVP_MD-BLAKE2.pod | 5 EVP_MD-BLAKE2 - The BLAKE2 EVP_MD implementation
13 This implementation is only available with the default provider, and
30 This implementation supports the common gettable parameters described
|
| H A D | EVP_MD-RIPEMD160.pod | 5 EVP_MD-RIPEMD160 - The RIPEMD160 EVP_MD implementation
13 This implementation is available in both the default and legacy providers, and is
19 This implementation supports the common gettable parameters described
|
| /freebsd/crypto/openssl/doc/man3/ |
| H A D | EVP_CIPHER_meth_new.pod | 76 implementation.
110 implementation.
114 Set this if the implementation's init() function should be called even
119 Set this to have the implementation's ctrl() function called with
125 is left to the implementation.
127 B<EVP_CIPHER> with this flag set, the implementation's ctrl() function
137 Making a key with random content is left to the implementation.
138 This is done by calling the implementation's ctrl() function with the
144 Set this to have the implementation's ctrl() function called with
147 implementation specific data block has been copied.
[all …]
|
| H A D | OSSL_ENCODER_CTX_new_for_pkey.pod | 50 L<EVP_KEYMGMT(3)> implementation associated with I<pkey> to build a list of
56 If no suitable encoder implementation is found,
60 the B<OSSL_ENCODER_CTX> and missing encoder implementation, and allows it to
63 OSSL_ENCODER_CTX_set_cipher() tells the implementation what cipher
66 implementation dependent. The implementation may implement the cipher
68 it. If the implementation supports fetching the cipher, then it may
73 OSSL_ENCODER_CTX_set_passphrase() gives the implementation a
80 implementation can use to prompt for a pass phrase, giving the caller the
|
| H A D | EC_GFp_simple_method.pod | 34 implementation method must be provided. The functions described here all return a const pointer to …
35 …THOD> structure that can be passed to EC_GROUP_NEW. It is important that the correct implementation
38 For F2^m curves there is only one implementation choice, i.e. EC_GF2_simple_method.
40 For Fp curves the lowest common denominator implementation is the EC_GFp_simple_method implementati…
43 offers an implementation optimised for use with NIST recommended curves (NIST curves are available …
|
| H A D | EVP_KDF.pod | 68 B<EVP_KDF> is a type that holds the implementation of a KDF.
72 =head2 Algorithm implementation fetching
74 EVP_KDF_fetch() fetches an implementation of a KDF I<algorithm>, given
92 EVP_KDF_CTX_new() creates a new context for the KDF implementation I<kdf>.
111 EVP_KDF_get_params() retrieves details about the implementation
132 defined by the implementation.
159 EVP_KDF_is_a() returns 1 if I<kdf> is an implementation of an
162 EVP_KDF_get0_provider() returns the provider that holds the implementation
167 implementations, calls the given function I<fn> with the implementation method
179 the I<kdf> implementation
[all...] |
| H A D | OSSL_ALGORITHM.pod | 15 const OSSL_DISPATCH *implementation;
43 Multiple names / identities allow a specific algorithm implementation to be
73 or canonical name, on a per algorithm implementation basis.
82 algorithm implementation, and is used by the appropriate fetching
84 a finer grained lookup of an algorithm implementation, which is useful in
90 =item I<implementation>
93 functions of a particular algorithm implementation.
|