| /freebsd/crypto/openssl/providers/ |
| H A D | defltprov.c | 34 #define ALGC(NAMES, FUNC, CHECK) { { NAMES, "provider=default", FUNC }, CHECK }
60 if (p != NULL && !OSSL_PARAM_set_utf8_ptr(p, "OpenSSL Default Provider")) in deflt_get_params()
103 { PROV_NAMES_SHA1, "provider=default", ossl_sha1_functions },
104 { PROV_NAMES_SHA2_224, "provider=default", ossl_sha224_functions },
105 { PROV_NAMES_SHA2_256, "provider=default", ossl_sha256_functions },
106 { PROV_NAMES_SHA2_256_192, "provider=default", ossl_sha256_192_functions },
107 { PROV_NAMES_SHA2_384, "provider=default", ossl_sha384_functions },
108 { PROV_NAMES_SHA2_512, "provider=default", ossl_sha512_functions },
109 { PROV_NAMES_SHA2_512_224, "provider=default", ossl_sha512_224_functions },
110 { PROV_NAMES_SHA2_512_256, "provider=default", ossl_sha512_256_functions },
[all …]
|
| /freebsd/crypto/openssl/ |
| H A D | README-PROVIDERS.md | 5 - [The Default Provider](#the-default-provider)
6 - [The Legacy Provider](#the-legacy-provider)
7 - [The FIPS Provider](#the-fips-provider)
8 - [The Base Provider](#the-base-provider)
9 - [The Null Provider](#the-null-provider)
16 algorithm is used via the high level APIs a provider is selected. It is that
17 provider implementation that actually does the required work. There are five
20 Documentation about writing providers is available on the [provider(7)]
23 [provider(7)]: https://www.openssl.org/docs/manmaster/man7/provider.html
25 The Default Provider
[all …]
|
| /freebsd/crypto/openssl/doc/internal/man3/ |
| H A D | ossl_provider_new.pod | 23 - internal provider routines
27 #include "internal/provider.h"
50 * Activate the Provider
51 * If the Provider is a module, the module will be loaded
58 /* Return pointer to the provider's context */
65 int (*cb)(OSSL_PROVIDER *provider,
76 /* Thin wrappers around calls to the provider */
93 int ossl_provider_set_operation_bit(OSSL_PROVIDER *provider, size_t bitnum);
94 int ossl_provider_test_operation_bit(OSSL_PROVIDER *provider, size_t bitnum,
105 to handle a provider, regardless of if it's built in to the
[all …]
|
| /freebsd/crypto/openssl/doc/man3/ |
| H A D | OSSL_PROVIDER.pod | 16 - provider routines
20 #include <openssl/provider.h>
39 int (*cb)(OSSL_PROVIDER *provider, void *cbdata),
74 implementation providers (see L<provider(7)> for information on what a
75 provider is).
76 A provider can be built in to the application or the OpenSSL
95 OSSL_PROVIDER_add_builtin() is used to add a built in provider to
97 provider name with a provider initialization function.
100 OSSL_PROVIDER_load() loads and initializes a provider.
101 This may simply initialize a provider that was previously added with
[all …]
|
| /freebsd/secure/lib/libcrypto/man/man3/ |
| H A D | OSSL_PROVIDER.3 | 75 \&\- provider routines
79 \& #include <openssl/provider.h>
98 \& int (*cb)(OSSL_PROVIDER *provider, void *cbdata),
133 implementation providers (see \fBprovider\fR\|(7) for information on what a
134 provider is).
135 A provider can be built in to the application or the OpenSSL
153 \&\fBOSSL_PROVIDER_add_builtin()\fR is used to add a built in provider to
155 provider name with a provider initialization function.
158 \&\fBOSSL_PROVIDER_load()\fR loads and initializes a provider.
159 This may simply initialize a provider that was previously added with
[all …]
|
| /freebsd/usr.sbin/bluetooth/sdpd/ |
| H A D | provider.c | 2 * provider.c
30 * $Id: provider.c,v 1.5 2004/01/13 01:54:39 max Exp $
39 #include "provider.h"
41 static TAILQ_HEAD(, provider) providers = TAILQ_HEAD_INITIALIZER(providers);
46 * Register Service Discovery provider.
85 * Register new provider for a given profile, bdaddr and session.
92 provider_p provider = calloc(1, sizeof(*provider)); in provider_register() local
94 if (provider != NULL) { in provider_register()
95 provider->data = malloc(datalen); in provider_register()
96 if (provider->data != NULL) { in provider_register()
[all …]
|
| /freebsd/crypto/openssl/doc/man7/ |
| H A D | provider.pod | 5 provider - OpenSSL operation implementation providers
11 #include <openssl/provider.h>
17 This page contains information useful to provider authors.
19 A I<provider>, in OpenSSL terms, is a unit of code that provides one
34 =head2 Provider section in DESCRIPTION
36 A I<provider> offers an initialization function, as a set of base
51 I<handle> is the OpenSSL library object for the provider, and works
53 the provider.
54 For the provider itself, it is passed to some of the functions given in the
59 L<provider-base(7)>.
[all …]
|
| H A D | provider-kem.pod | 5 provider-kem - The kem library E<lt>-E<gt> provider functions
50 This documentation is primarily aimed at provider authors. See L<provider(7)>
59 F<libcrypto> and the provider in L<OSSL_DISPATCH(3)> arrays via
60 L<OSSL_ALGORITHM(3)> arrays that are returned by the provider's
62 (see L<provider-base(7)/Provider Functions>).
96 In order to be a consistent set of functions a provider must implement
110 See L<provider-keymgmt(7)> for further details.
114 OSSL_FUNC_kem_newctx() should create and return a pointer to a provider side
118 The parameter I<provctx> is the provider context generated during provider
119 initialisation (see L<provider(7)>).
[all …]
|
| H A D | provider-base.pod | 5 provider-base
6 - The basic OpenSSL library E<lt>-E<gt> provider functions
99 int (*create_cb)(const OSSL_CORE_HANDLE *provider,
101 int (*remove_cb)(const OSSL_CORE_HANDLE *provider,
112 /* Functions offered by the provider to libcrypto */
129 F<libcrypto> and the provider in L<OSSL_DISPATCH(3)> arrays, in the call
130 of the provider initialization function. See L<provider(7)/Provider>
148 provider):
203 For I<*out> (the L<OSSL_DISPATCH(3)> array passed from the provider to
224 The core_thread_start() function informs the core that the provider has stated
[all …]
|
| /freebsd/release/ |
| H A D | Makefile.vagrant | 65 .for PROVIDER in ${VAGRANT_PROVIDERS}
66 CLEANFILES+= vagrant-do-package-${PROVIDER} ${VAGRANT_TARGET}.${PROVIDER}.box
67 CLEANDIRS+= ${PROVIDER}
68 VAGRANT_UPLOAD_TGTS+= vagrant-do-upload-${PROVIDER}
70 ${PROVIDER}:
71 @mkdir -p ${PROVIDER}
73 ${VAGRANT_TARGET}.${PROVIDER}.box: ${PROVIDER} cw-vagrant-${PROVIDER} vagrant-create-${PROVIDER}-me…
74 @echo "==> PACKAGING: ${VAGRANT_TARGET}.${PROVIDER}.box in `pwd`"
75 @cp vagrant-${PROVIDER}.vmdk ${PROVIDER}/vagrant.vmdk
76 . if ${PROVIDER} == "virtualbox"
[all …]
|
| /freebsd/tools/regression/geom/ConfCmp/ |
| H A D | a1.conf | 14 <provider><ref>0x80bf880</ref></provider>
26 <provider><ref>0x80bf800</ref></provider>
38 <provider><ref>0x80bf780</ref></provider>
50 <provider><ref>0x80bf600</ref></provider>
62 <provider><ref>0x80bf480</ref></provider>
74 <provider><ref>0x80bf400</ref></provider>
86 <provider><ref>0x80bf380</ref></provider>
98 <provider><ref>0x80bf300</ref></provider>
110 <provider><ref>0x80bf280</ref></provider>
122 <provider><ref>0x80bf100</ref></provider>
[all …]
|
| H A D | a1a.conf | 14 <provider><ref>0x90bf880</ref></provider>
26 <provider><ref>0x90bf800</ref></provider>
38 <provider><ref>0x90bf780</ref></provider>
50 <provider><ref>0x90bf600</ref></provider>
62 <provider><ref>0x90bf480</ref></provider>
74 <provider><ref>0x90bf400</ref></provider>
86 <provider><ref>0x90bf380</ref></provider>
98 <provider><ref>0x90bf300</ref></provider>
110 <provider><ref>0x90bf280</ref></provider>
122 <provider><ref>0x90bf100</ref></provider>
[all …]
|
| H A D | a1d.conf | 14 <provider><ref>0x80bf880</ref></provider>
26 <provider><ref>0x80bf800</ref></provider>
38 <provider><ref>0x80bf780</ref></provider>
50 <provider><ref>0x80bf600</ref></provider>
62 <provider><ref>0x80bf480</ref></provider>
74 <provider><ref>0x80bf400</ref></provider>
86 <provider><ref>0x80bf380</ref></provider>
98 <provider><ref>0x80bf300</ref></provider>
110 <provider><ref>0x80bf280</ref></provider>
122 <provider><ref>0x80bf100</ref></provider>
[all …]
|
| H A D | a1b.conf | 14 <provider><ref>0x80bf880</ref></provider>
26 <provider><ref>0x80bf800</ref></provider>
38 <provider><ref>0x80bf780</ref></provider>
50 <provider><ref>0x80bf600</ref></provider>
62 <provider><ref>0x80bf480</ref></provider>
74 <provider><ref>0x80bf400</ref></provider>
86 <provider><ref>0x80bf380</ref></provider>
98 <provider><ref>0x80bf300</ref></provider>
110 <provider><ref>0x80bf280</ref></provider>
122 <provider><ref>0x80bf100</ref></provider>
[all …]
|
| H A D | a1c.conf | 14 <provider><ref>0x80bf880</ref></provider>
26 <provider><ref>0x80bf800</ref></provider>
38 <provider><ref>0x80bf780</ref></provider>
50 <provider><ref>0x80bf600</ref></provider>
62 <provider><ref>0x80bf480</ref></provider>
74 <provider><ref>0x80bf400</ref></provider>
86 <provider><ref>0x80bf380</ref></provider>
98 <provider><ref>0x80bf300</ref></provider>
110 <provider><ref>0x80bf280</ref></provider>
122 <provider><ref>0x80bf100</ref></provider>
[all …]
|
| /freebsd/secure/lib/libcrypto/man/man7/ |
| H A D | provider.7 | 57 .IX Title "PROVIDER 7ossl"
58 .TH PROVIDER 7ossl 2025-09-16 3.5.3 OpenSSL
64 provider \- OpenSSL operation implementation providers
67 #include <openssl/provider.h>
72 This page contains information useful to provider authors.
74 A \fIprovider\fR, in OpenSSL terms, is a unit of code that provides one
88 .SS Provider
89 .IX Subsection "Provider"
90 A \fIprovider\fR offers an initialization function, as a set of base
107 \&\fIhandle\fR is the OpenSSL library object for the provider, and works
[all …]
|
| H A D | provider-base.7 | 57 .IX Title "PROVIDER-BASE 7ossl"
58 .TH PROVIDER-BASE 7ossl 2025-09-16 3.5.3 OpenSSL
64 provider\-base
65 \&\- The basic OpenSSL library <\-> provider functions
158 \& int (*create_cb)(const OSSL_CORE_HANDLE *provider,
160 \& int (*remove_cb)(const OSSL_CORE_HANDLE *provider,
171 \& /* Functions offered by the provider to libcrypto */
188 \&\fIlibcrypto\fR and the provider in \fBOSSL_DISPATCH\fR\|(3) arrays, in the call
189 of the provider initialization function. See "Provider" in \fBprovider\fR\|(7)
209 provider):
[all …]
|
| H A D | ossl-guide-libraries-introduction.7 | 95 A provider in OpenSSL is a component that collects together algorithm
98 provider loaded that contains an implementation of it. OpenSSL comes with a
103 built-in provider is one that is either already present in \f(CW\*(C`libcrypto\*(C'\fR or one
107 If you don't load a provider explicitly (either in program code or via config)
108 then the OpenSSL built-in "default" provider will be automatically loaded.
120 a provider is loaded, it is only loaded within the scope of a given library
145 of any given algorithm might be available. For example the OpenSSL FIPS provider
147 available in the OpenSSL default provider.
152 string of "provider=default" could be used to force the selection to only
153 consider algorithm implementations in the default provider.
[all …]
|
| H A D | provider-digest.7 | 57 .IX Title "PROVIDER-DIGEST 7ossl"
58 .TH PROVIDER-DIGEST 7ossl 2025-09-16 3.5.3 OpenSSL
64 provider\-digest \- The digest library <\-> provider functions
108 This documentation is primarily aimed at provider authors. See \fBprovider\fR\|(7)
116 \&\fIlibcrypto\fR and the provider in \fBOSSL_DISPATCH\fR\|(3) arrays via
117 \&\fBOSSL_ALGORITHM\fR\|(3) arrays that are returned by the provider's
119 (see "Provider Functions" in \fBprovider\-base\fR\|(7)).
163 \&\fBOSSL_FUNC_digest_newctx()\fR should create and return a pointer to a provider side
167 The parameter \fIprovctx\fR is the provider context generated during provider
168 initialisation (see \fBprovider\fR\|(7)).
[all …]
|
| H A D | provider-signature.7 | 57 .IX Title "PROVIDER-SIGNATURE 7ossl"
58 .TH PROVIDER-SIGNATURE 7ossl 2025-09-16 3.5.3 OpenSSL
64 provider\-signature \- The signature library <\-> provider functions
161 This documentation is primarily aimed at provider authors. See \fBprovider\fR\|(7)
170 \&\fIlibcrypto\fR and the provider in \fBOSSL_DISPATCH\fR\|(3) arrays via
171 \&\fBOSSL_ALGORITHM\fR\|(3) arrays that are returned by the provider's
173 (see "Provider Functions" in \fBprovider\-base\fR\|(7)).
274 indicating the key types supported by the provider for signature operations.
281 See \fBprovider\-keymgmt\fR\|(7) for further details.
284 \&\fBOSSL_FUNC_signature_newctx()\fR should create and return a pointer to a provider side
[all …]
|
| /freebsd/crypto/openssl/doc/designs/ |
| H A D | ossl-provider-load-ex.md | 4 Currently any provider run-time activation requires the presence of the
6 provider will be activated with some default settings, that may or may not
13 provider (where different applications may use different devices with different
15 also usable for FIPS provider.
24 intended to configure the provider at load time.
27 provider can be initialized from the config file where the values are
28 represented as strings and provider init function has to deal with it.
38 provider <https://github.com/latchset/pkcs11-provider> also provides a set of
42 1. Configure a provider in the config file, activate on demand
43 2. Load/activate a provider run-time with parameters
[all …]
|
| /freebsd/sys/contrib/openzfs/module/icp/core/ |
| H A D | kcf_prov_tabs.c | 35 * The provider table is indexed by crypto_provider_id_t. Each
36 * element of the table contains a pointer to a provider descriptor,
40 * provider descriptors.
53 * a crypto provider registers with kcf. The provider calls the
57 * A provider unregisters by calling crypto_unregister_provider()
85 * Add a provider to the provider table. If no free entry can be found
86 * for the new provider, returns CRYPTO_HOST_MEMORY. Otherwise, add
87 * the provider to the table, initialize the pd_prov_id field
88 * of the specified provider descriptor to the index in that table,
90 * provider when pointed to by a table entry.
[all …]
|
| /freebsd/crypto/openssl/test/recipes/ |
| H A D | 30-test_evp_fetch_prov.t | 31 { args => [ '-property', 'provider=default' ],
32 message => 'using property "provider=default"' },
33 { args => [ '-property', 'provider!=fips' ],
34 message => 'using property "provider!=fips"' },
35 { args => [ '-property', 'provider!=default', '-fetchfail' ],
37 'using property "provider!=default" is expected to fail' },
38 { args => [ '-property', 'provider=fips', '-fetchfail' ],
40 'using property "provider=fips" is expected to fail' } ] }
49 { args => [ '-property', 'provider=fips' ],
50 message => 'using property "provider=fips"' },
[all …]
|
| /freebsd/contrib/llvm-project/lldb/source/Plugins/Language/ObjC/ |
| H A D | ObjCLanguage.cpp | 259 "SEL summary provider", "SEL", objc_flags); in LoadObjCFormatters()
262 "SEL summary provider", "struct objc_selector", objc_flags); in LoadObjCFormatters()
265 "SEL summary provider", "objc_selector", objc_flags); in LoadObjCFormatters()
268 "SEL summary provider", "objc_selector *", objc_flags); in LoadObjCFormatters()
271 "SEL summary provider", "SEL *", objc_flags); in LoadObjCFormatters()
275 "Class summary provider", "Class", objc_flags); in LoadObjCFormatters()
353 "NSArray summary provider", "NSArray", appkit_flags); in LoadObjCFormatters()
356 "NSArray summary provider", "NSConstantArray", appkit_flags); in LoadObjCFormatters()
359 "NSArray summary provider", "NSMutableArray", appkit_flags); in LoadObjCFormatters()
362 "NSArray summary provider", "__NSArray in LoadObjCFormatters()
[all...] |
| /freebsd/crypto/openssl/doc/internal/man7/ |
| H A D | EVP_PKEY.pod | 24 explained further down, in L</Export cache for provider operations>),
43 =item provider-native origin
46 key data (see L<provider-keymgmt(7)>). The internal key in the
47 B<EVP_PKEY> is a pointer to that key data held by the provider, and
69 internal key is a provider key then the return value from functions such as
71 copy are not reflected back in the provider key.
73 Internal provider native keys are also possible to be modified, if the
93 in L</Export cache for provider operations>.
95 For provider native origin keys, this doesn't require any help from
104 =head2 Export cache for provider operations
[all …]
|