| /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 dde79dfdedfe0e73006a0cf912fdde1ff109dfbc5ba6ecab319c938bc4275950 providers/implementations/asymcip…
624 c2f1b12c64fc369dfc3b9bc9e76a76de7280e6429adaee55d332eb1971ad1879 providers/implementations/ciphers…
625 6ba7d817081cf0d87ba7bfb38cd9d70e41505480bb8bc796ef896f68d4514ea6 providers/implementations/ciphers…
626 c20072ecf42c87f9fad2ea241d358f57ed2a04cf0cc51bdb8cb5086172f6fc8a providers/implementations/ciphers…
627 7668e5c1cac474ad7b0f28aa78ca885edf44815fe4a606a6cd328b3c02fac25a providers/implementations/ciphers…
628 26e0f28523b416ba4067e471061f5a11fd76f5dc8bfe57ce37a137cf5667630b providers/implementations/ciphers…
629 6d2ab2e059ef38fad342d4c65eebd533c08a2092bb174ff3566c6604e175c5a4 providers/implementations/ciphers…
630 1b6d31811a6729f0c75c7c7ccfb7d3a75ab6001605b229593187918a592da789 providers/implementations/ciphers…
631 00f36bf48e522dbb5ec71df0ec13e387955fa3672e6ff90e8a412ae95c4a642f providers/implementations/ciphers…
632 4812d59ab6e1380f38e0c7cc0d7995eb6a2abf1438cedf233b939a17c4111482 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
90 Available input types depend on the implementations that available providers
93 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
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
|
| /freebsd/secure/lib/libcrypto/man/man3/ |
| H A D | OSSL_DECODER_CTX_new_for_pkey.3 | 98 \&\fBOSSL_DECODER_CTX\fR, finds all applicable decoder implementations and sets
108 \&\fBEVP_KEYMGMT\fR\|(3) implementations, and then builds a list of all potential
109 decoder implementations that may be able to process the encoded input into
110 data suitable for \fBEVP_PKEY\fRs. All these implementations are implicitly
113 The search of decoder implementations can be limited with \fIinput_type\fR and
115 NULL is valid for both of them and signifies that the decoder implementations
121 The search of decoder implementations can also be limited with \fIkeytype\fR
123 NULL and zero are valid and signify that the decoder implementations will
148 Available input types depend on the implementations that available providers
151 Among the known input types that OpenSSL decoder implementations offer
[all …]
|
| H A D | EVP_KDF.3 | 221 implementations, calls the given function \fIfn\fR with the implementation method
239 Some KDF implementations require a password.
240 For those KDF implementations that support it, this parameter sets the password.
243 Some KDF implementations can take a non-secret unique cryptographic salt.
244 For those KDF implementations that support it, this parameter sets the salt.
249 Some KDF implementations require an iteration count.
250 For those KDF implementations that support it, this parameter sets the
264 For KDF implementations that use an underlying computation MAC, digest or
271 implementations.
274 Some KDF implementations require a key.
[all …]
|
| H A D | OSSL_ENCODER_CTX_new_for_pkey.3 | 100 \&\fBOSSL_ENCODER_CTX\fR, finds all applicable encoder implementations and sets
110 applicable encoder implementations that are used to process the \fIpkey\fR into
112 \&\fIoutput_structure\fR if that's relevant. All these implementations are
126 directly itself or by other implementations, or it may choose to fetch
145 implementations.
147 OpenSSL has built in implementations for the following output types:
167 These are only 'hints' since the encoder implementations are free to
|
| /freebsd/secure/lib/libcrypto/man/man7/ |
| H A D | ossl-guide-libraries-introduction.7 | 96 implementations (for example an implementation of the symmetric encryption
146 supplies alternative implementations of many of the same algorithms that are
153 consider algorithm implementations in the default provider.
236 contains all of the most commonly used algorithm implementations. Should it be
237 needed (if other providers are loaded and offer implementations of the same
239 search criterion for these implementations. The default provider includes all
250 algorithm implementations for encoding and decoding of OpenSSL keys.
252 implementations of the same algorithms), the property query string
253 "provider=base" can be used as a search criterion for these implementations.
254 Some encoding and decoding algorithm implementations are not FIPS algorithm
[all …]
|
| H A D | openssl-glossary.7 | 86 the algorithm implementations in the Base Provider are also available in the
99 implementations. It is loaded by default if no other provider is available. All
100 the algorithm implementations in the Base Provider are also available in the
127 implementations, applying selection criteria (via a property query string), and
135 An OpenSSL Provider that contains OpenSSL algorithm implementations that have
148 An OpenSSL Provider that contains algorithm implementations that are considered
167 An OpenSSL Provider that contains no algorithm implementations. This can be
213 A property is a way of classifying and selecting algorithm implementations.
215 implementations in the default provider have the property "provider=default".
234 implementations. Providers can come from OpenSSL itself or from third parties.
|
| /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.
|
| /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/sys/contrib/openzfs/module/icp/include/ |
| H A D | generic_impl.c | 32 * It's ment for easier maintaining multiple implementations of
41 /* Two default implementations */
52 /* Hold all supported implementations */
67 /* check the supported implementations */
77 /* Move supported implementations into generic_supp_impls */ in generic_impl_init()
91 /* get number of supported implementations */
156 /* check mandatory implementations */ in generic_impl_setname()
168 /* 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 …]
|
| /freebsd/usr.sbin/apm/ |
| H A D | apm.8 | 70 These options are not necessary for almost all APM implementations,
71 but for some implementations whose
136 Some APM implementations do not support parameters needed by
142 Some APM implementations cannot handle events such as pushing the
144 On such implementations, the system
|
| /freebsd/contrib/libarchive/libarchive/ |
| H A D | tar.5 | 58 implementations was 10240 bytes or 20 records.
59 This is still the default for most implementations
99 Early tar implementations only stored regular files (including
112 In particular, this field was ignored by early tar implementations
127 Note that many early implementations of tar used signed arithmetic
148 Early tar implementations varied in how they terminated these fields.
156 Early implementations filled the numeric fields with leading spaces.
160 For best portability, modern implementations should fill the numeric
167 program and many system implementations from the late 1980s
187 by compliant implementations o
[all...] |
| /freebsd/share/man/man4/man4.i386/ |
| H A D | apm.4 | 70 Some APM implementations execute the HLT
86 On some implementations that do not support CPU clock slowdown, APM
128 Many, if not most, of the implementations of APM-bios in laptops
147 Some APM implementations cannot handle events such as pushing the
149 On such implementations, the system
|
| /freebsd/contrib/ncurses/man/ |
| H A D | curs_getstr.3x | 185 SVr3 and early SVr4 curses implementations did not reject function keys;
194 string by those implementations was predictable but not useful
206 As of 2018, some implementations count it, some do not:
222 however most implementations
266 Other implementations differ in their treatment of special characters:
269 other implementations do not modify the \fIraw\fP mode,
285 where other implementations allow one to enter those characters in the buffer.
|
| /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()
117 /* Else some implementations only support sizes up to 2^16 */ in verify()
264 printf("Implementations:"); in main()
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()
|