| /freebsd-14.2/crypto/openssl/providers/ |
| H A D | fips.module.sources | 555 providers/implementations/include/prov/implementations.h
560 providers/implementations/kdfs/hkdf.c
561 providers/implementations/kdfs/kbkdf.c
562 providers/implementations/kdfs/pbkdf2.c
563 providers/implementations/kdfs/pbkdf2.h
565 providers/implementations/kdfs/sshkdf.c
566 providers/implementations/kdfs/sskdf.c
568 providers/implementations/kdfs/x942kdf.c
569 providers/implementations/kem/rsa_kem.c
582 providers/implementations/rands/crngt.c
[all …]
|
| H A D | fips-sources.checksums | 555 …5a0cfa1dbbc78e0f60a9012f3a34e711cafb09c7b5 providers/implementations/include/prov/implementations…
560 6091dd22e716fbe6c7c94524cdee6ad4432a572f2d3c4d360dcafafa3902d692 providers/implementations/kdfs/hk…
561 a62e3af09f5af84dcf36f951ba4ac90ca1694adaf3747126186020b155f94186 providers/implementations/kdfs/kb…
562 e0644e727aacfea4da3cf2c4d2602d7ef0626ebb760b6467432ffd54d5fbb24d providers/implementations/kdfs/pb…
563 c0778565abff112c0c5257329a7750ec4605e62f26cc36851fa1fbee6e03c70c providers/implementations/kdfs/pb…
565 9cc42a4b0a8089e6d1be64637dbb9e41bd21ae5e3386022a27a8f29308ad25c9 providers/implementations/kdfs/ss…
566 8571556d77d10e8edc98212473a38f09632e3f19e9995dde89ee6c95f2e84ccf providers/implementations/kdfs/ss…
568 4d4a6d9a562d2dcfec941d3f113a544663b5ac2fbe4accd89ec70c1cc11751d0 providers/implementations/kdfs/x9…
569 58acb0ff36bf7e463ba714b347b714eccab9fda77c4ca6bacc3a55e6d2ce5ad9 providers/implementations/kem/rsa…
582 bf30274dd6b528ae913984775bd8f29c6c48c0ef06d464d0f738217727b7aa5c providers/implementations/rands/c…
[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
79 INCLUDE[$DEFAULTGOAL]=implementations/include
89 INCLUDE[$BASEGOAL]=implementations/include
[all …]
|
| /freebsd-14.2/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
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
93 Among the known input types that OpenSSL decoder implementations offer
100 Available input structures depend on the implementations that available
103 Among the known input structures that OpenSSL decoder implementations
[all …]
|
| H A D | EVP_KDF.pod | 189 Some KDF implementations require a 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.
227 For those KDF implementations that support it, this octet string parameter
241 Used by implementations that use a MAC with a variable output size (KMAC).
[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
67 directly itself or by other implementations, or it may choose to fetch
87 implementations.
89 OpenSSL has built in implementations for the following output types:
114 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-14.2/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-14.2/secure/lib/libcrypto/modules/legacy/ |
| H A D | Makefile | 32 .PATH: ${LCRYPTO_SRC}/providers/implementations/ciphers \
33 ${LCRYPTO_SRC}/providers/implementations/digests \
34 ${LCRYPTO_SRC}/providers/implementations/kdfs \
|
| /freebsd-14.2/usr.bin/sed/ |
| H A D | POSIX | 18 1. 32V and BSD derived implementations of sed strip the text
75 (e.g. /foo/!!!p). Historic implementations allow any number of
102 11. Historical implementations do not output the change text of a c
120 Historic implementations did not output the text in the above
130 13. Historical implementations allow an output suppressing #n at the
139 command. Historic sed implementations behave differently for "ls |
154 As historic sed implementations always discarded the backslash,
159 is not true for historic implementations or this implementation
164 Historic implementations of sed assigned different locations to
186 23. Historic implementations handle empty RE's in a special way: the
[all …]
|
| /freebsd-14.2/crypto/openssl/doc/man7/ |
| 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 | crypto.pod | 15 provided by this library are used by the OpenSSL implementations of TLS and
32 implementations such as in a hardware security module (HSM).
48 implementations. In order to use an algorithm you must have at least one
103 Fetching is the process of looking through the available implementations,
115 algorithm implementations in the default provider.
186 L<EVP_DigestSignInit(3)> and friends, all fetch the implementations
280 implementations.
376 algorithm implementations for encoding and decoding for OpenSSL keys.
378 implementations of the same algorithms), the property query string
395 these implementations. All approved algorithm implementations in the FIPS
[all …]
|
| 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
66 The AES-SIV and AES-WRAP mode implementations do not support streaming. That
70 The AES-XTS implementations allow streaming to be performed, but each
|
| 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
|
| /freebsd-14.2/contrib/cortex-strings/ |
| H A D | README | 6 Various implementations of these routines are provided, including generic
7 implementations for ARMv7-A cores with/without Neon, Thumb2 implementations
8 and generic implementations for cores supporting AArch64.
22 implementations gathered from around the Internet
24 check and report on the different implementations.
101 Some of the implementations have been collected from other
|
| /freebsd-14.2/sys/contrib/device-tree/Bindings/mfd/ |
| H A D | google,cros-ec.yaml | 23 For implementations of the EC connected through I2C.
26 For implementations of the EC connected through SPI.
29 For implementations of the FPMCU connected through SPI.
34 For implementations of the EC connected through RPMSG.
37 For implementations of the EC connected through UART.
57 Some implementations of the EC include a small nvram space used to
|
| 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-14.2/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.
89 file), and in the case of implementations for commercial hardware
127 for testing and examination of ENGINE implementations. Basic usage
134 implementations that aren't pre-compiled and linked into OpenSSL-based
[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-14.2/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-14.2/sys/contrib/device-tree/Bindings/arm/ |
| H A D | psci.yaml | 41 For implementations complying to PSCI versions prior to 0.2.
45 For implementations complying to PSCI 0.2.
56 For implementations complying to PSCI 1.0.
119 helps to implement support for OSI mode and OS implementations may choose
|
| /freebsd-14.2/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
|