| /freebsd/crypto/openssl/providers/ |
| H A D | fips.module.sources | 503 providers/implementations/asymciphers/rsa_enc.c
504 providers/implementations/ciphers/cipher_aes.c
505 providers/implementations/ciphers/cipher_aes.h
506 providers/implementations/ciphers/cipher_aes_cbc_hmac_sha.c
507 providers/implementations/ciphers/cipher_aes_cbc_hmac_sha.h
508 providers/implementations/ciphers/cipher_aes_cbc_hmac_sha1_hw.c
509 providers/implementations/ciphers/cipher_aes_cbc_hmac_sha256_hw.c
510 providers/implementations/ciphers/cipher_aes_ccm.c
511 providers/implementations/ciphers/cipher_aes_ccm.h
512 providers/implementations/ciphers/cipher_aes_ccm_hw.c
[all …]
|
| H A D | fips-sources.checksums | 503 99baeec10374301e90352ab637056104a8ea28a6880804f44c640d0c9ee16eba providers/implementations/asymcip…
504 4db1826ecce8b60cb641bcd7a61430ec8cef73d2fe3cbc06aa33526afe1c954a providers/implementations/ciphers…
505 6ba7d817081cf0d87ba7bfb38cd9d70e41505480bb8bc796ef896f68d4514ea6 providers/implementations/ciphers…
506 aef500281e7cd5a25a806a9bd45ec00a5b73984673202527dac5896fbcc9fa9c providers/implementations/ciphers…
507 7668e5c1cac474ad7b0f28aa78ca885edf44815fe4a606a6cd328b3c02fac25a providers/implementations/ciphers…
508 26e0f28523b416ba4067e471061f5a11fd76f5dc8bfe57ce37a137cf5667630b providers/implementations/ciphers…
509 6d2ab2e059ef38fad342d4c65eebd533c08a2092bb174ff3566c6604e175c5a4 providers/implementations/ciphers…
510 f37c3cf9e2e6fcfcbed941f3670b790fe09990349db72eb065bef51705d46e96 providers/implementations/ciphers…
511 00f36bf48e522dbb5ec71df0ec13e387955fa3672e6ff90e8a412ae95c4a642f providers/implementations/ciphers…
512 6337b570e0dc4e98af07aa9704254d3ab958cf605584e250fbd76cd1d2a25ac7 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
79 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 requir
[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 | 174 \&\fB\s-1OSSL_DECODER_CTX\s0\fR, finds all applicable decoder implementations and sets
184 \&\s-1\fBEVP_KEYMGMT\s0\fR\|(3) implementations, and then builds a list of all potential
185 decoder implementations that may be able to process the encoded input into
186 data suitable for \fB\s-1EVP_PKEY\s0\fRs. All these implementations are implicitly
189 The search of decoder implementations can be limited with \fIinput_type\fR and
191 \&\s-1NULL\s0 is valid for both of them and signifies that the decoder implementations
197 The search of decoder implementations can also be limited with \fIkeytype\fR
199 \&\s-1NULL\s0 and zero are valid and signify that the decoder implementations will
224 Available input types depend on the implementations that available providers
227 Among the known input types that OpenSSL decoder implementations offer
[all …]
|
| H A D | EVP_KDF.3 | 297 implementations, calls the given function \fIfn\fR with the implementation method
316 Some \s-1KDF\s0 implementations require a password.
317 For those \s-1KDF\s0 implementations that support it, this parameter sets the password.
321 Some \s-1KDF\s0 implementations can take a non-secret unique cryptographic salt.
322 For those \s-1KDF\s0 implementations that support it, this parameter sets the salt.
328 Some \s-1KDF\s0 implementations require an iteration count.
329 For those \s-1KDF\s0 implementations that support it, this parameter sets the
347 For \s-1KDF\s0 implementations that use an underlying computation \s-1MAC,\s0 digest or
354 implementations.
358 Some \s-1KDF\s0 implementations require a key.
[all …]
|
| H A D | OSSL_ENCODER_CTX_new_for_pkey.3 | 176 \&\fB\s-1OSSL_ENCODER_CTX\s0\fR, finds all applicable encoder implementations and sets
186 applicable encoder implementations that are used to process the \fIpkey\fR into
188 \&\fIoutput_structure\fR if that's relevant. All these implementations are
202 directly itself or by other implementations, or it may choose to fetch
221 implementations.
223 OpenSSL has built in implementations for the following output types:
243 These are only 'hints' since the encoder implementations are free to
|
| /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/crypto/openssl/doc/man7/ |
| H A D | crypto.pod | 15 provided by this library are used by the OpenSSL implementations of TLS and
28 implementations available for use. For example the RSA algorithm is available as
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.
361 contains all of the most commonly used algorithm implementations. Should it be
362 needed (if other providers are loaded and offer implementations of the same
[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/secure/lib/libcrypto/man/man7/ |
| H A D | crypto.7 | 148 provided by this library are used by the OpenSSL implementations of \s-1TLS\s0 and
160 implementations available for use. For example the \s-1RSA\s0 algorithm is available as
164 implementations such as in a hardware security module (\s-1HSM\s0).
178 implementations. In order to use an algorithm you must have at least one
230 Fetching is the process of looking through the available implementations,
241 algorithm implementations in the default provider.
303 \&\fBEVP_DigestSignInit\fR\|(3) and friends, all fetch the implementations
383 implementations.
476 contains all of the most commonly used algorithm implementations. Should it be
477 needed (if other providers are loaded and offer implementations of the same
[all …]
|
| H A D | openssl-glossary.7 | 162 the algorithm implementations in the Base Provider are also available in the
175 implementations. It is loaded by default if no other provider is available. All
176 the algorithm implementations in the Base Provider are also available in the
204 implementations, applying selection criteria (via a property query string), and
212 An OpenSSL Provider that contains OpenSSL algorithm implementations that have
225 An OpenSSL Provider that contains algorithm implementations that are considered
244 An OpenSSL Provider that contains no algorithm implementations. This can be
291 A property is a way of classifying and selecting algorithm implementations.
293 implementations in the default provider have the property \*(L"provider=default\*(R".
312 implementations. Providers can come from OpenSSL itself or from third parties.
|
| /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/ |
| H A D | Makefile | 370 # providers/implementations/asymciphers
373 # providers/implementations/ciphers
403 # providers/implementations/digests
413 # providers/implementations/encode_decode
419 # providers/implementations/exchange
424 # providers/implementations/kdfs
428 # providers/implementations/kem
431 # providers/implementations/keymgmt
435 # providers/implementations/macs
442 # 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()
|
| /freebsd/crypto/openssl/doc/internal/man7/ |
| H A D | deprecation.pod | 54 L</Implementations to be removed> below.
66 units. See L</Implementations to remain internally> below.
91 =head2 Implementations to be removed
99 * Suppress deprecation warnings for RSA low level implementations that are
114 =head2 Implementations to remain internally
|