| /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 | 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
|
| H A D | EC_GFp_simple_method.pod | 32 The Elliptic Curve library provides a number of different implementations through a single common i…
41 other implementations are based on this one. EC_GFp_mont_method builds on EC_GFp_simple_method but …
47 optimised implementations for the NIST P224, P256 and P521 curves respectively. Note, however, that…
48 implementations are not available on all platforms.
|
| H A D | PKCS12_PBE_keyivgen.pod | 41 implementations.
51 implementations.
69 are used to select appropriate algorithm implementations.
|
| /freebsd/contrib/arm-optimized-routines/networking/test/ |
| H A D | chksum.c | 73 } implementations[] = variable
88 for (int i = 0; implementations[i].name != NULL; i++) in find_impl()
90 if (strcmp(implementations[i].name, name) == 0) in find_impl()
265 for (int i = 0; implementations[i].name != NULL; i++) in main()
267 printf(" %s", implementations[i].name); in main()
278 CKSUM_FP = implementations[IMPL].cksum_fp; in main()
291 printf("Implementation: %s\n", implementations[IMPL].name); in main()
|
| /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 | evp.pod | 71 implementations. If ENGINE implementations of ciphers or digests are registered
73 implementations automatically in preference to built in software
74 implementations. For more information, consult the engine(3) man page.
|
| H A D | OSSL_PROVIDER-legacy.pod | 9 The OpenSSL legacy provider supplies OpenSSL implementations of algorithms
18 The implementations in this provider specifically has this property
33 make sure to get implementations of this provider and none other.
|
| H A D | EVP_CIPHER-AES.pod | 5 EVP_CIPHER-AES - The AES EVP_CIPHER implementations
68 The AES-SIV and AES-WRAP mode implementations do not support streaming. That
72 The AES-XTS implementations allow streaming to be performed, but each
|
| H A D | EVP_MD-SHAKE.pod | 6 - The SHAKE / KECCAK family EVP_MD implementations
59 The SHAKE-128 and SHAKE-256 implementations do not have any default digest
89 Since OpenSSL 3.4 the SHAKE-128 and SHAKE-256 implementations have no default
|
| H A D | EVP_MD-common.pod | 5 EVP_MD-common - The OpenSSL EVP_MD implementations, common things
9 All the OpenSSL EVP_MD implementations understand the following
|
| H A D | ossl-guide-libcrypto-introduction.pod | 13 provided by this library are used by the OpenSSL implementations of TLS and
26 implementations available for use. For example the RSA algorithm is available as
30 implementations such as in a hardware security module (HSM).
49 Fetching is the process of looking through the available implementations,
83 Each provider supports a list of algorithm implementations. See the provider
84 specific documentation for information on the algorithm implementations
127 L<EVP_DigestSignInit(3)>, all fetch the implementations implicitly. Usually the
199 implementations.
369 Encoders and decoders are just algorithm implementations in the same way as
|
| /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/secure/lib/libcrypto/modules/legacy/ |
| H A D | Makefile | 59 ${LCRYPTO_SRC}/providers/implementations/ciphers \
60 ${LCRYPTO_SRC}/providers/implementations/digests \
61 ${LCRYPTO_SRC}/providers/implementations/kdfs \
|
| /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 …]
|
| H A D | README-PROVIDERS.md | 15 Providers are containers for algorithm implementations. Whenever a cryptographic
29 algorithm implementations. If an application doesn't specify anything else
57 The FIPS provider contains a sub-set of the algorithm implementations available
62 implementations in this provider compared to the equivalent algorithm in the
78 implementations. In order to guarantee that the default provider is not
|
| /freebsd/crypto/openssl/doc/designs/ |
| H A D | passing-algorithmidentifier-parameters.md | 8 parameter field to symmetric cipher provider implementations. We currently
10 provider implementations.
12 We do support passing them to legacy implementations of other types of
43 provider implementations alike in whatever way they see fit.
135 AlgorithmIdenfier parameter data to the backend implementations of
148 implementations *MUST NOT* share complex OpenSSL specific structures with
|
| /freebsd/sys/contrib/device-tree/Bindings/mfd/ |
| H A D | cros-ec.txt | 24 - google,cros-ec-spi-pre-delay: Some implementations of the EC need a little
28 - google,cros-ec-spi-msg-delay: Some implementations of the EC require some
41 - google,has-vbc-nvram: Some implementations of the EC include a small
|
| /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 …]
|
| /freebsd/sys/arm/arm/ |
| H A D | platform_if.m | 43 * implementations
44 * @brief A set of methods required by all platform implementations.
53 # Default implementations
|