| /freebsd/crypto/openssl/providers/ |
| H A D | fips.module.sources | 623 providers/implementations/asymciphers/rsa_enc.c
624 providers/implementations/ciphers/cipher_aes.c
625 providers/implementations/ciphers/cipher_aes.h
626 providers/implementations/ciphers/cipher_aes_cbc_hmac_sha.c
627 providers/implementations/ciphers/cipher_aes_cbc_hmac_sha.h
628 providers/implementations/ciphers/cipher_aes_cbc_hmac_sha1_hw.c
629 providers/implementations/ciphers/cipher_aes_cbc_hmac_sha256_hw.c
630 providers/implementations/ciphers/cipher_aes_ccm.c
631 providers/implementations/ciphers/cipher_aes_ccm.h
632 providers/implementations/ciphers/cipher_aes_ccm_hw.c
[all …]
|
| H A D | fips-sources.checksums | 623 d942921caa433ae9e62959b0ad1caad277b50d005ffc439c6d0e7b0886dba882 providers/implementations/asymcip…
624 c2f1b12c64fc369dfc3b9bc9e76a76de7280e6429adaee55d332eb1971ad1879 providers/implementations/ciphers…
625 6ba7d817081cf0d87ba7bfb38cd9d70e41505480bb8bc796ef896f68d4514ea6 providers/implementations/ciphers…
626 693a3a667bf13d3703601dc4d1daca9d890ca4f193ba26b8d77571f79507de16 providers/implementations/ciphers…
627 1b4f19be0c2bbea99e5fce0f93189c687a03cac634f0e37a51466ee7e3510735 providers/implementations/ciphers…
628 a579a933e7756b502510a42679e06dca2737bda9e53edda578e28eae56b98577 providers/implementations/ciphers…
629 4e5e5c6478cf72f6840aa5d9edc50fe27aaa3ea39a428f602056172b0f00d541 providers/implementations/ciphers…
630 1b6d31811a6729f0c75c7c7ccfb7d3a75ab6001605b229593187918a592da789 providers/implementations/ciphers…
631 00f36bf48e522dbb5ec71df0ec13e387955fa3672e6ff90e8a412ae95c4a642f providers/implementations/ciphers…
632 8049497bb1a3a6d5549d25ab31cf43afdf2e97ca789caed6502c19da3be44ae8 providers/implementations/ciphers…
[all …]
|
| H A D | build.info | 4 # libfips.a Contains all algorithm implementations that should
8 # liblegacy.a Contains all algorithm implementations that should
12 # libdefault.a Contains all algorithm implementations that should
17 # libfips.a the sources from providers/implementations.
30 # Code in providers/implementations/ should be written in such a way that
34 SUBDIRS=common implementations
45 # Enough of our implementations include prov/ciphercommon.h (present in
46 # providers/implementations/include), which includes crypto/*_platform.h
49 $COMMON_INCLUDES=../crypto ../include implementations/include common/include \
80 INCLUDE[$DEFAULTGOAL]=implementations/include
[all …]
|
| /freebsd/crypto/openssl/doc/man3/ |
| H A D | OPENSSL_armcap.pod | 37 performance preferences for some implementations which only make sense on
50 Effect: Enables various Armv7 Neon SIMD implementations.
67 Effect: Enables various Armv8.0 AES hardware-accelerated implementations.
76 Effect: Enables various Armv8.0 SHA1 hardware-accelerated implementations.
85 Effect: Enables various Armv8.0 SHA256 hardware-accelerated implementations.
104 Effect: Enables Armv8.2 SHA512 hardware-accelerated implementations.
113 Effect: Allows implementations to change their behaviour, dependant on the
133 Effect: Enables Armv8.2 SM3 hardware-accelerated implementations.
142 Effect: Enables Armv8.2 SM4 hardware-accelerated implementations.
151 Effect: Enables SHA3 hardware-accelerated implementations (see also
[all …]
|
| H A D | OSSL_DECODER_CTX_new_for_pkey.pod | 39 B<OSSL_DECODER_CTX>, finds all applicable decoder implementations and sets
49 L<EVP_KEYMGMT(3)> implementations, and then builds a list of all potential
50 decoder implementations that may be able to process the encoded input into
51 data suitable for B<EVP_PKEY>s. All these implementations are implicitly
54 The search of decoder implementations can be limited with I<input_type> and
56 NULL is valid for both of them and signifies that the decoder implementations
62 The search of decoder implementations can also be limited with I<keytype>
64 NULL and zero are valid and signify that the decoder implementations will
94 Available input types depend on the implementations that available providers
97 Among the known input types that OpenSSL decoder implementations offer
[all …]
|
| H A D | EVP_KDF.pod | 167 implementations, calls the given function I<fn> with the implementation method
189 Some KDF implementations require a password.
190 For those KDF implementations that support it, this parameter sets the password.
194 Some KDF implementations can take a non-secret unique cryptographic salt.
195 For those KDF implementations that support it, this parameter sets the salt.
201 Some KDF implementations require an iteration count.
202 For those KDF implementations that support it, this parameter sets the
215 For KDF implementations that use an underlying computation MAC, digest or
222 implementations.
226 Some KDF implementations require a key.
[all …]
|
| H A D | OSSL_ENCODER_CTX_new_for_pkey.pod | 41 B<OSSL_ENCODER_CTX>, finds all applicable encoder implementations and sets
51 applicable encoder implementations that are used to process the I<pkey> into
53 I<output_structure> if that's relevant. All these implementations are
71 directly itself or by other implementations, or it may choose to fetch
91 implementations.
93 OpenSSL has built in implementations for the following output types:
118 These are only 'hints' since the encoder implementations are free to
|
| /freebsd/secure/lib/libcrypto/man/man3/ |
| H A D | OSSL_DECODER_CTX_new_for_pkey.3 | 101 \&\fBOSSL_DECODER_CTX\fR, finds all applicable decoder implementations and sets
111 \&\fBEVP_KEYMGMT\fR\|(3) implementations, and then builds a list of all potential
112 decoder implementations that may be able to process the encoded input into
113 data suitable for \fBEVP_PKEY\fRs. All these implementations are implicitly
116 The search of decoder implementations can be limited with \fIinput_type\fR and
118 NULL is valid for both of them and signifies that the decoder implementations
124 The search of decoder implementations can also be limited with \fIkeytype\fR
126 NULL and zero are valid and signify that the decoder implementations will
155 Available input types depend on the implementations that available providers
158 Among the known input types that OpenSSL decoder implementations offer
[all …]
|
| H A D | OPENSSL_armcap.3 | 99 performance preferences for some implementations which only make sense on
109 Effect: Enables various Armv7 Neon SIMD implementations.
124 Effect: Enables various Armv8.0 AES hardware\-accelerated implementations.
132 Effect: Enables various Armv8.0 SHA1 hardware\-accelerated implementations.
140 Effect: Enables various Armv8.0 SHA256 hardware\-accelerated implementations.
157 Effect: Enables Armv8.2 SHA512 hardware\-accelerated implementations.
165 Effect: Allows implementations to change their behaviour, dependant on the
183 Effect: Enables Armv8.2 SM3 hardware\-accelerated implementations.
191 Effect: Enables Armv8.2 SM4 hardware\-accelerated implementations.
199 Effect: Enables SHA3 hardware\-accelerated implementations (see also
[all …]
|
| H A D | EVP_KDF.3 | 224 implementations, calls the given function \fIfn\fR with the implementation method
242 Some KDF implementations require a password.
243 For those KDF implementations that support it, this parameter sets the password.
246 Some KDF implementations can take a non\-secret unique cryptographic salt.
247 For those KDF implementations that support it, this parameter sets the salt.
252 Some KDF implementations require an iteration count.
253 For those KDF implementations that support it, this parameter sets the
267 For KDF implementations that use an underlying computation MAC, digest or
274 implementations.
277 Some KDF implementations require a key.
[all …]
|
| H A D | OSSL_ENCODER_CTX_new_for_pkey.3 | 103 \&\fBOSSL_ENCODER_CTX\fR, finds all applicable encoder implementations and sets
113 applicable encoder implementations that are used to process the \fIpkey\fR into
115 \&\fIoutput_structure\fR if that\*(Aqs relevant. All these implementations are
133 directly itself or by other implementations, or it may choose to fetch
152 implementations.
154 OpenSSL has built in implementations for the following output types:
174 These are only \*(Aqhints\*(Aq since the encoder implementations are free to
|
| /freebsd/secure/lib/libcrypto/man/man7/ |
| H A D | ossl-guide-libraries-introduction.7 | 99 implementations (for example an implementation of the symmetric encryption
149 supplies alternative implementations of many of the same algorithms that are
156 consider algorithm implementations in the default provider.
239 contains all of the most commonly used algorithm implementations. Should it be
240 needed (if other providers are loaded and offer implementations of the same
242 search criterion for these implementations. The default provider includes all
253 algorithm implementations for encoding and decoding of OpenSSL keys.
255 implementations of the same algorithms), the property query string
256 "provider=base" can be used as a search criterion for these implementations.
257 Some encoding and decoding algorithm implementations are not FIPS algorithm
[all …]
|
| H A D | openssl-glossary.7 | 89 the algorithm implementations in the Base Provider are also available in the
102 implementations. It is loaded by default if no other provider is available. All
103 the algorithm implementations in the Base Provider are also available in the
130 implementations, applying selection criteria (via a property query string), and
138 An OpenSSL Provider that contains OpenSSL algorithm implementations that have
151 An OpenSSL Provider that contains algorithm implementations that are considered
170 An OpenSSL Provider that contains no algorithm implementations. This can be
216 A property is a way of classifying and selecting algorithm implementations.
218 implementations in the default provider have the property "provider=default".
237 implementations. Providers can come from OpenSSL itself or from third parties.
|
| H A D | property.7 | 67 property \- Properties, a selection mechanism for algorithm implementations
71 multiple implementations of an algorithm will be used.
112 .SS Implementations
113 .IX Subsection "Implementations"
176 result in implementations that have "fips=yes".
182 disallow any implementations with "fips=yes" rather than not caring about the
192 It is a convention among OpenSSL provider implementations to define a property with this name. It …
198 OpenSSL provider implementations do not define a property with this name.
204 It is a convention among OpenSSL provider implementations to define a property with this name where…
|
| /freebsd/crypto/openssl/doc/man7/ |
| H A D | ossl-guide-libraries-introduction.pod | 39 implementations (for example an implementation of the symmetric encryption
91 supplies alternative implementations of many of the same algorithms that are
98 consider algorithm implementations in the default provider.
185 contains all of the most commonly used algorithm implementations. Should it be
186 needed (if other providers are loaded and offer implementations of the same
188 search criterion for these implementations. The default provider includes all
200 algorithm implementations for encoding and decoding of OpenSSL keys.
202 implementations of the same algorithms), the property query string
203 "provider=base" can be used as a search criterion for these implementations.
204 Some encoding and decoding algorithm implementations are not FIPS algorithm
[all …]
|
| H A D | openssl-glossary.pod | 34 the algorithm implementations in the Base Provider are also available in the
49 implementations. It is loaded by default if no other provider is available. All
50 the algorithm implementations in the Base Provider are also available in the
81 implementations, applying selection criteria (via a property query string), and
90 An OpenSSL Provider that contains OpenSSL algorithm implementations that have
105 An OpenSSL Provider that contains algorithm implementations that are considered
127 An OpenSSL Provider that contains no algorithm implementations. This can be
175 A property is a way of classifying and selecting algorithm implementations.
177 implementations in the default provider have the property "provider=default".
198 implementations. Providers can come from OpenSSL itself or from third parties.
|
| H A D | property.pod | 5 property - Properties, a selection mechanism for algorithm implementations
10 multiple implementations of an algorithm will be used.
52 =head2 Implementations section in DESCRIPTION
136 result in implementations that have "fips=yes".
142 disallow any implementations with "fips=yes" rather than not caring about the
157 It is a convention among OpenSSL provider implementations to define a property with this name. It …
163 OpenSSL provider implementations do not define a property with this name.
169 It is a convention among OpenSSL provider implementations to define a property with this name where…
|
| /freebsd/usr.bin/sed/ |
| H A D | POSIX | 17 1. 32V and BSD derived implementations of sed strip the text
74 (e.g. /foo/!!!p). Historic implementations allow any number of
101 11. Historical implementations do not output the change text of a c
119 Historic implementations did not output the text in the above
129 13. Historical implementations allow an output suppressing #n at the
138 command. Historic sed implementations behave differently for "ls |
153 As historic sed implementations always discarded the backslash,
158 is not true for historic implementations or this implementation
163 Historic implementations of sed assigned different locations to
181 22. Historic implementations of sed ignore the RE delimiter characters
[all …]
|
| /freebsd/contrib/bearssl/samples/ |
| H A D | custom_profile.c | 29 * configures a list of cipher suites and algorithm implementations.
147 * Note that with current implementations, SHA-224 and SHA-256 in example_client_profile()
162 * configured (failure to provide needed implementations may in example_client_profile()
169 * Public-key algorithm implementations. in example_client_profile()
184 * Normally, you use the "default" implementations, obtained in example_client_profile()
186 * implementations that are deemed "best" for the current in example_client_profile()
188 * implementations". Selecting the default implementation is a in example_client_profile()
191 * Nevertheless, specific implementations may be selected in example_client_profile()
206 * There are no less than 10 elliptic curve implementations: in example_client_profile()
227 * implementations directly will result in smaller code, but in example_client_profile()
[all …]
|
| /freebsd/contrib/llvm-project/libc/src/__support/FPUtil/generic/ |
| H A D | README.md | 1 This directory contains machine independent implementations of floating point
2 operations. The implementations are nested in the namespace
4 implementations from machine dependent implementations. Consider the example of
11 `long double` flavor. By putting the generic implementations in a separate
|
| /freebsd/sys/contrib/openzfs/module/icp/include/ |
| H A D | generic_impl.c | 22 * It's ment for easier maintaining multiple implementations of
31 /* Two default implementations */
42 /* Hold all supported implementations */
57 /* check the supported implementations */
67 /* Move supported implementations into generic_supp_impls */ in generic_impl_init()
81 /* get number of supported implementations */
146 /* check mandatory implementations */ in generic_impl_setname()
158 /* check all supported implementations */ in generic_impl_setname()
|
| /freebsd/secure/lib/libcrypto/modules/legacy/ |
| H A D | Makefile | 32 # providers/implementations/digests
36 # providers/implementations/kdfs
59 ${LCRYPTO_SRC}/providers/implementations/ciphers \
60 ${LCRYPTO_SRC}/providers/implementations/digests \
61 ${LCRYPTO_SRC}/providers/implementations/kdfs \
|
| /freebsd/secure/lib/libcrypto/ |
| H A D | Makefile | 411 # providers/implementations/asymciphers
414 # providers/implementations/ciphers
439 # providers/implementations/digests
447 # providers/implementations/encode_decode
454 # providers/implementations/exchange
459 # providers/implementations/kdfs
464 # providers/implementations/kem
467 # providers/implementations/keymgmt
472 # providers/implementations/macs
479 # providers/implementations/rands
[all …]
|
| /freebsd/crypto/openssl/ |
| H A D | README-ENGINES.md | 8 interface for adding alternative implementations of cryptographic
14 users who need to maintain or support existing ENGINE implementations.
19 Built-in ENGINE implementations
22 There are currently built-in ENGINE implementations for the following
29 In addition, dynamic binding to external ENGINE implementations is now
43 the ENGINE model so that alternative implementations of existing
45 ENGINE implementations.
84 development and/or testing of the implementations, and *usually* (with no
89 file), and in the case of implementations for commercial hardware
127 for testing and examination of ENGINE implementations. Basic usage
[all …]
|
| /freebsd/crypto/openssl/crypto/engine/ |
| H A D | README.md | 50 ciphers simultaneously registers cipher *types* and cipher *implementations* -
62 Ie. all implementations *have* to come from an ENGINE, but we get round that by
69 implementations of certain functionality. Touching any part of any kind of
82 for a fallback ENGINE that encapsulates default implementations - we can simply
88 and the existing EVP API functions that return "software" implementations and
97 implementations *registered*. As such, a NULL ENGINE pointer is stored in the
113 course, when one of these "private" cipher implementations is hooked into
151 implementations of "des_cbc" are added or removed. This behaviour can be
163 implementations. In other words, the ENGINE_TABLE for RSA will either be empty,
174 registered any of its implementations (to do so would link all class "table"
[all …]
|