| /freebsd/contrib/llvm-project/compiler-rt/include/xray/ |
| H A D | xray_log_interface.h | 11 // APIs for installing a new logging implementation.
16 /// to replace the default runtime-controllable implementation that comes with
17 /// compiler-rt/xray. The "flight data recorder" (FDR) mode implementation uses
19 /// compiler-rt/lib/xray_fdr_logging.{h,cc} for details of that implementation.
34 /// // Once that's done, we can now attempt to configure the implementation.
42 /// // When the log implementation has had the chance to initialize, we can
51 /// // If we want to stop the implementation, we can then finalize it (before
59 /// // chance to see that the implementation is already finalized. Also, at
78 /// // implementation supports exporting this data directly).
89 /// implementation first. Some implementations might stay in an "off" state when
[all …]
|
| /freebsd/contrib/bearssl/inc/ |
| H A D | bearssl_block.h | 45 * For a block cipher implementation, up to three separate sets of
311 * `aes_big` is a "classical" AES implementation, using tables. It
315 * `aes_small` is an AES implementation optimized for code size. It
319 * `aes_ct` is a constant-time implementation of AES; its code is about
322 * implementation should thus be considered to be the "default" AES in
324 * non-constant-time implementation is safe, or an architecture-specific
325 * constant-time implementation can be used (e.g. using dedicated
328 * `aes_ct64` is another constant-time implementation of AES. It is
342 * `des_tab` is a classic, table-based implementation of DES/3DES. It
345 * `des_ct` is an constant-time implementation of DES/3DES. It is
[all …]
|
| H A D | bearssl_ec.h | 46 * Only "named curves" are supported. Each EC implementation supports
56 * An EC implementation is incarnated by a `br_ec_impl` instance, that
62 * by this implementation.
268 * \brief Type for an EC implementation.
275 * is supported. E.g. an implementation supporting both NIST P-256
418 * \brief EC implementation "i31".
420 * This implementation internally uses generic code for modular integers,
427 * \brief EC implementation "i15".
429 * This implementation internally uses generic code for modular integers,
436 * \brief EC implementation "m15" for P-256.
[all …]
|
| H A D | bearssl_rsa.h | 133 * - The **i32** implementation internally represents big integers
137 * - The **i31** implementation uses 32-bit integers, each containing
138 * 31 bits worth of integer data. The i31 implementation is somewhat
139 * faster than the i32 implementation (the reduced integer size makes
143 * - The **i62** implementation is similar to the i31 implementation,
145 * opcode. This implementation is available only on architectures
148 * - The **i15** implementation uses 16-bit integers, each containing
535 * length, and 1 is returned. The implementation is responsible for
884 * \brief Get the RSA "i62" implementation (public key operations),
887 * \return the implementation, or 0.
[all …]
|
| /freebsd/contrib/libcbor/src/cbor/ |
| H A D | callbacks.h | 110 /** Dummy callback implementation - does nothing */
113 /** Dummy callback implementation - does nothing */
116 /** Dummy callback implementation - does nothing */
119 /** Dummy callback implementation - does nothing */
122 /** Dummy callback implementation - does nothing */
125 /** Dummy callback implementation - does nothing */
128 /** Dummy callback implementation - does nothing */
131 /** Dummy callback implementation - does nothing */
134 /** Dummy callback implementation - does nothing */
137 /** Dummy callback implementation - does nothing */
[all …]
|
| /freebsd/secure/lib/libcrypto/man/man7/ |
| H A D | ossl-guide-libcrypto-introduction.7 | 83 a "default" implementation suitable for general use, and a "fips" implementation
102 In order to use an algorithm an implementation for it must first be "fetched".
105 the implementation that will be used.
112 implementation from a provider. This fetched object can then be passed to other
115 can be used to explicitly fetch a digest algorithm implementation. The user is
146 implementation. See
149 The algorithm implementation that is fetched can then be used with other diverse
156 associated implementation, such as \fBEVP_sha256\fR\|(3), \fBEVP_aes_128_cbc\fR\|(3),
162 \&\fBEVP_CipherInit_ex\fR\|(3), the actual implementation to be used is
167 is supplied. In this case an algorithm implementation is implicitly fetched
[all …]
|
| H A D | provider-encoder.7 | 117 The ENCODER implementation may be part of a chain, where data is
119 implementation to encode an object to DER (that object is assumed to
177 The name of an implementation should match the type of object it handles.
178 For example, an implementation that encodes an RSA key should be named "RSA".
179 Likewise, an implementation that further encodes DER should be named "DER".
182 decoder implementation, can be used to further specify details about an
183 implementation:
186 This property is used to specify what type of output the implementation
195 An implementation with that output type outputs human readable text, making
196 that implementation suitable for \f(CW\*(C`\-text\*(C'\fR output in diverse \fBopenssl\fR\|(1)
[all …]
|
| H A D | provider-decoder.7 | 118 The DECODER implementation may be part of a chain, where data is
120 implementation to decode an object from PEM to DER, and another one
170 The name of an implementation should match the target type of object
171 it decodes. For example, an implementation that decodes an RSA key
172 should be named "RSA". Likewise, an implementation that decodes DER data
176 decoder implementation, can be used to further specify details about an
177 implementation:
180 This property is used to specify what format of input the implementation
189 An implementation with that input type decodes PEM formatted data.
192 An implementation with that input type decodes DER formatted data.
[all …]
|
| /freebsd/crypto/openssl/doc/man7/ |
| H A D | ossl-guide-libcrypto-introduction.pod | 27 a "default" implementation suitable for general use, and a "fips" implementation
48 In order to use an algorithm an implementation for it must first be "fetched".
51 the implementation that will be used.
59 implementation from a provider. This fetched object can then be passed to other
62 can be used to explicitly fetch a digest algorithm implementation. The user is
98 implementation. See
103 The algorithm implementation that is fetched can then be used with other diverse
111 associated implementation, such as L<EVP_sha256(3)>, L<EVP_aes_128_cbc(3)>,
117 L<EVP_CipherInit_ex(3)>, the actual implementation to be used is
122 is supplied. In this case an algorithm implementation is implicitly fetched
[all …]
|
| H A D | provider-encoder.pod | 59 The ENCODER implementation may be part of a chain, where data is
61 implementation to encode an object to DER (that object is assumed to
126 The name of an implementation should match the type of object it handles.
127 For example, an implementation that encodes an RSA key should be named "RSA".
128 Likewise, an implementation that further encodes DER should be named "DER".
131 decoder implementation, can be used to further specify details about an
132 implementation:
138 This property is used to specify what type of output the implementation
149 An implementation with that output type outputs human readable text, making
150 that implementation suitable for C<-text> output in diverse L<openssl(1)>
[all …]
|
| H A D | provider-decoder.pod | 59 The DECODER implementation may be part of a chain, where data is
61 implementation to decode an object from PEM to DER, and another one
108 The name of an implementation should match the target type of object
109 it decodes. For example, an implementation that decodes an RSA key
110 should be named "RSA". Likewise, an implementation that decodes DER data
114 decoder implementation, can be used to further specify details about an
115 implementation:
121 This property is used to specify what format of input the implementation
132 An implementation with that input type decodes PEM formatted data.
136 An implementation with that input type decodes DER formatted data.
[all …]
|
| /freebsd/crypto/openssl/providers/implementations/include/prov/ |
| H A D | names.h | 271 #define PROV_DESCS_HKDF_SIGN "OpenSSL HKDF via EVP_PKEY implementation"
281 #define PROV_DESCS_TLS1_PRF_SIGN "OpenSSL TLS1_PRF via EVP_PKEY implementation"
285 #define PROV_DESCS_SCRYPT_SIGN "OpenSSL SCRYPT via EVP_PKEY implementation"
297 #define PROV_DESCS_HMAC_SIGN "OpenSSL HMAC via EVP_PKEY implementation"
299 #define PROV_DESCS_CMAC_SIGN "OpenSSL CMAC via EVP_PKEY implementation"
301 #define PROV_DESCS_SIPHASH_SIGN "OpenSSL SIPHASH via EVP_PKEY implementation"
303 #define PROV_DESCS_POLY1305_SIGN "OpenSSL POLY1305 via EVP_PKEY implementation"
327 #define PROV_DESCS_EC "OpenSSL EC implementation"
329 #define PROV_DESCS_ECDH "OpenSSL ECDH implementation"
340 #define PROV_DESCS_ECDSA "OpenSSL ECDSA implementation"
[all …]
|
| /freebsd/usr.bin/sed/ |
| H A D | POSIX | 39 backslash in front of it. This implementation follows the BSD
48 implementation permits whitespace but does not require it.
52 POSIX. This implementation permits whitespace but does not
59 is a cleanup, and is followed by this implementation.
76 one might reverse the behaviour.) This implementation follows
84 command. This implementation follows historic practice and
97 This implementation follows historic practice.
105 any particular purpose, this implementation follows the POSIX
122 However, the current practice adopted by this implementation,
131 does not specify this. This implementation follows historical
[all …]
|
| /freebsd/sys/contrib/libsodium/src/libsodium/randombytes/ |
| H A D | randombytes.c | 30 static const randombytes_implementation *implementation; variable
47 if (implementation == NULL) { in randombytes_init_if_needed()
48 implementation = RANDOMBYTES_DEFAULT_IMPLEMENTATION; in randombytes_init_if_needed()
56 implementation = impl; in randombytes_set_implementation()
66 return implementation->implementation_name(); in randombytes_implementation_name()
77 return implementation->random(); in randombytes_random()
90 if (implementation->stir != NULL) { in randombytes_stir()
91 implementation->stir(); in randombytes_stir()
132 if (implementation->uniform != NULL) { in randombytes_uniform()
133 return implementation->uniform(upper_bound); in randombytes_uniform()
[all …]
|
| /freebsd/contrib/llvm-project/clang/lib/APINotes/ |
| H A D | APINotesReader.cpp | 611 class APINotesReader::Implementation { class in clang::api_notes::APINotesReader
732 APINotesReader::Implementation::getIdentifier(llvm::StringRef Str) { in getIdentifier()
747 APINotesReader::Implementation::getSelector(ObjCSelectorRef Selector) { in getSelector()
769 bool APINotesReader::Implementation::readControlBlock( in readControlBlock()
856 bool APINotesReader::Implementation::readIdentifierBlock( in readIdentifierBlock()
932 bool APINotesReader::Implementation::readContextBlock( in readContextBlock()
1022 bool APINotesReader::Implementation::readObjCPropertyBlock( in readObjCPropertyBlock()
1099 bool APINotesReader::Implementation::readObjCMethodBlock( in readObjCMethodBlock()
1174 bool APINotesReader::Implementation::readCXXMethodBlock( in readCXXMethodBlock()
1249 bool APINotesReader::Implementation::readObjCSelectorBlock( in readObjCSelectorBlock()
[all …]
|
| /freebsd/sys/contrib/openzfs/ |
| H A D | COPYRIGHT | 18 * Skein Checksum Implementation: module/icp/algs/skein/THIRDPARTYLICENSE
19 * AES Implementation: module/icp/asm-x86_64/aes/THIRDPARTYLICENSE.gladman
20 * AES Implementation: module/icp/asm-x86_64/aes/THIRDPARTYLICENSE.openssl
21 * PBKDF2 Implementation: lib/libzfs/THIRDPARTYLICENSE.openssl
22 * SPL Implementation: module/os/linux/spl/THIRDPARTYLICENSE.gplv2
23 * GCM Implementation: module/icp/asm-x86_64/modes/THIRDPARTYLICENSE.cryptogams
24 * GCM Implementation: module/icp/asm-x86_64/modes/THIRDPARTYLICENSE.openssl
25 * GHASH Implementation: module/icp/asm-x86_64/modes/THIRDPARTYLICENSE.cryptogams
26 * GHASH Implementation: module/icp/asm-x86_64/modes/THIRDPARTYLICENSE.openssl
|
| /freebsd/sys/contrib/openzfs/include/os/freebsd/spl/sys/ |
| H A D | isa_defs.h | 37 * implementation choices for Solaris on a processor.
46 * Implementation Choices:
49 * This specifies the compiler data type implementation as specified in
56 * and Solaris implementation. Due to its historical standing,
61 * implementation for 64-bit ABIs such as SPARC V9.
113 * Define the appropriate "implementation choices".
136 * Define the appropriate "implementation choices".
146 * Define the appropriate "implementation choices"
156 * Define the appropriate "implementation choices"
166 * Define the appropriate "implementation choices".
[all …]
|
| /freebsd/sys/contrib/libsodium/src/libsodium/crypto_stream/chacha20/ |
| H A D | stream_chacha20.c | 17 static const crypto_stream_chacha20_implementation *implementation = variable
56 return implementation->stream(c, clen, n, k); in crypto_stream_chacha20()
63 return implementation->stream_ietf(c, clen, n, k); in crypto_stream_chacha20_ietf()
72 return implementation->stream_xor_ic(c, m, mlen, n, ic, k); in crypto_stream_chacha20_xor_ic()
81 return implementation->stream_ietf_xor_ic(c, m, mlen, n, ic, k); in crypto_stream_chacha20_ietf_xor_ic()
89 return implementation->stream_xor_ic(c, m, mlen, n, 0U, k); in crypto_stream_chacha20_xor()
97 return implementation->stream_ietf_xor_ic(c, m, mlen, n, 0U, k); in crypto_stream_chacha20_ietf_xor()
115 implementation = &crypto_stream_chacha20_ref_implementation; in _crypto_stream_chacha20_pick_best_implementation()
119 implementation = &crypto_stream_chacha20_dolbeau_avx2_implementation; in _crypto_stream_chacha20_pick_best_implementation()
125 implementation = &crypto_stream_chacha20_dolbeau_ssse3_implementation; in _crypto_stream_chacha20_pick_best_implementation()
|
| /freebsd/crypto/krb5/src/util/verto/ |
| H A D | verto.h | 82 * Creates a new event context using an optionally specified implementation
86 * event loop implementation, you should not call this function, but instead
88 * NAME is the implementation you wish to use.
94 * where you have a need to choose an implementation at run time, usually
96 * wish to remain implementation agnostic. In this later case, you should
98 * implementation to use.
101 * implementation specified. If the implementation specified is not
103 * named implementation, NULL is returned. The parameter 'impl' can specify:
104 * * The full path to an implementation library
105 * * The name of the implementation library (i.e. - "glib" or "libev")
[all …]
|
| /freebsd/sys/contrib/libsodium/src/libsodium/crypto_stream/salsa20/ |
| H A D | stream_salsa20.c | 22 static const crypto_stream_salsa20_implementation *implementation = variable
25 static const crypto_stream_salsa20_implementation *implementation = variable
51 return implementation->stream(c, clen, n, k); in crypto_stream_salsa20()
60 return implementation->stream_xor_ic(c, m, mlen, n, ic, k); in crypto_stream_salsa20_xor_ic()
68 return implementation->stream_xor_ic(c, m, mlen, n, 0U, k); in crypto_stream_salsa20_xor()
81 implementation = &crypto_stream_salsa20_xmm6_implementation; in _crypto_stream_salsa20_pick_best_implementation()
83 implementation = &crypto_stream_salsa20_ref_implementation; in _crypto_stream_salsa20_pick_best_implementation()
89 implementation = &crypto_stream_salsa20_xmm6int_avx2_implementation; in _crypto_stream_salsa20_pick_best_implementation()
95 implementation = &crypto_stream_salsa20_xmm6int_sse2_implementation; in _crypto_stream_salsa20_pick_best_implementation()
|
| /freebsd/sys/contrib/libsodium/src/libsodium/crypto_onetimeauth/poly1305/ |
| H A D | onetimeauth_poly1305.c | 14 static const crypto_onetimeauth_poly1305_implementation *implementation = variable
21 return implementation->onetimeauth(out, in, inlen, k); in crypto_onetimeauth_poly1305()
30 return implementation->onetimeauth_verify(h, in, inlen, k); in crypto_onetimeauth_poly1305_verify()
37 return implementation->onetimeauth_init(state, key); in crypto_onetimeauth_poly1305_init()
45 return implementation->onetimeauth_update(state, in, inlen); in crypto_onetimeauth_poly1305_update()
52 return implementation->onetimeauth_final(state, out); in crypto_onetimeauth_poly1305_final()
83 implementation = &crypto_onetimeauth_poly1305_donna_implementation; in _crypto_onetimeauth_poly1305_pick_best_implementation()
86 implementation = &crypto_onetimeauth_poly1305_sse2_implementation; in _crypto_onetimeauth_poly1305_pick_best_implementation()
|
| /freebsd/crypto/openssl/doc/man3/ |
| H A D | EVP_CIPHER_meth_new.pod | 76 implementation.
110 implementation.
114 Set this if the implementation's init() function should be called even
119 Set this to have the implementation's ctrl() function called with
125 is left to the implementation.
127 B<EVP_CIPHER> with this flag set, the implementation's ctrl() function
137 Making a key with random content is left to the implementation.
138 This is done by calling the implementation's ctrl() function with the
144 Set this to have the implementation's ctrl() function called with
147 implementation specific data block has been copied.
[all …]
|
| /freebsd/secure/lib/libcrypto/man/man3/ |
| H A D | EVP_CIPHER_meth_new.3 | 137 implementation.
163 implementation.
166 Set this if the implementation's \fBinit()\fR function should be called even
170 Set this to have the implementation's \fBctrl()\fR function called with
175 is left to the implementation.
177 \&\fBEVP_CIPHER\fR with this flag set, the implementation's \fBctrl()\fR function
185 Making a key with random content is left to the implementation.
186 This is done by calling the implementation's \fBctrl()\fR function with the
191 Set this to have the implementation's \fBctrl()\fR function called with
194 implementation specific data block has been copied.
[all …]
|
| /freebsd/contrib/llvm-project/clang/include/clang/AST/ |
| H A D | LexicallyOrderedRecursiveASTVisitor.h | 29 /// some declarations, like Objective-C @implementation declarations
32 /// In particular, Objective-C @implementation declarations may contain
35 /// @implementation MyClass
42 /// Clang's AST stores these declarations outside of the @implementation
52 /// corresponding TraverseDecl for the @implementation returns. This ensures
54 /// @implementation is preserved while traversing the AST. Note that the
55 /// current implementation doesn't mix these declarations with the declarations
56 /// contained in the @implementation, so the traversal of all of the
57 /// declarations in the @implementation still doesn't follow the lexical order.
67 // Objective-C @implementation declarations should not trigger early exit in TraverseObjCImplementationDecl()
[all …]
|
| /freebsd/crypto/openssl/doc/designs/quic-design/ |
| H A D | debugging.md | 16 implementation which is not directly observable from the network.
22 information on the internal state of a QUIC implementation. For example,
23 packet capture cannot directly tell you when an implementation deems a packet
35 implementation
39 - Con: No direct information on internal states of a QUIC implementation
55 Any process using the libssl QUIC implementation will then automatically write
70 Currently this implementation tracks qvis's qlog support, as that is the
74 protocol implementation, for the purposes of reducing the volume of logging
101 written directly by a QUIC implementation for debugging purposes. The purpose of
106 For the OpenSSL QUIC implementation, OpenSSL must be instructed to save a keylog
[all …]
|