Home
last modified time | relevance | path

Searched full:provider (Results 1 – 25 of 1318) sorted by relevance

12345678910>>...53

/freebsd/crypto/openssl/
H A DREADME-PROVIDERS.md5 - [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/man3.0/man7/provider.html
25 The Default Provider
[all …]
/freebsd/crypto/openssl/doc/internal/man3/
H A Dossl_provider_new.pod23 - internal provider routines
27 #include "internal/provider.h"
53 * Activate the Provider
54 * If the Provider is a module, the module will be loaded
61 /* Return pointer to the provider's context */
68 int (*cb)(OSSL_PROVIDER *provider,
79 /* Thin wrappers around calls to the provider */
94 int ossl_provider_set_operation_bit(OSSL_PROVIDER *provider, size_t bitnum);
95 int ossl_provider_test_operation_bit(OSSL_PROVIDER *provider, size_t bitnum,
106 to handle a provider, regardles
[all...]
/freebsd/crypto/openssl/doc/man3/
H A DOSSL_PROVIDER.pod13 - provider routines
17 #include <openssl/provider.h>
30 int (*cb)(OSSL_PROVIDER *provider, void *cbdata),
59 implementation providers (see L<provider(7)> for information on what a
60 provider is).
61 A provider can be built in to the application or the OpenSSL
75 OSSL_PROVIDER_add_builtin() is used to add a built in provider to
77 provider name with a provider initialization function.
80 OSSL_PROVIDER_load() loads and initializes a provider.
81 This may simply initialize a provider that was previously added with
[all …]
/freebsd/crypto/openssl/providers/
H A Ddefltprov.c34 #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_384, "provider=default", ossl_sha384_functions },
107 { PROV_NAMES_SHA2_512, "provider=default", ossl_sha512_functions },
108 { PROV_NAMES_SHA2_512_224, "provider=default", ossl_sha512_224_functions },
109 { PROV_NAMES_SHA2_512_256, "provider=default", ossl_sha512_256_functions },
112 { PROV_NAMES_SHA3_224, "provider=default", ossl_sha3_224_functions },
[all …]
/freebsd/usr.sbin/bluetooth/sdpd/
H A Dprovider.c2 * 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 Dprovider.pod5 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 Dprovider-base.pod5 provider-base
6 - The basic OpenSSL library E<lt>-E<gt> provider functions
89 int (*create_cb)(const OSSL_CORE_HANDLE *provider,
91 int (*remove_cb)(const OSSL_CORE_HANDLE *provider,
102 /* Functions offered by the provider to libcrypto */
119 F<libcrypto> and the provider in L<OSSL_DISPATCH(3)> arrays, in the call
120 of the provider initialization function. See L<provider(7)/Provider>
138 provider):
185 For I<*out> (the L<OSSL_DISPATCH(3)> array passed from the provider to
206 The core_thread_start() function informs the core that the provider has stated
[all …]
H A Dprovider-kem.pod5 provider-kem - The kem library E<lt>-E<gt> provider functions
44 This documentation is primarily aimed at provider authors. See L<provider(7)>
53 F<libcrypto> and the provider in L<OSSL_DISPATCH(3)> arrays via
54 L<OSSL_ALGORITHM(3)> arrays that are returned by the provider's
56 (see L<provider-base(7)/Provider Functions>).
88 In order to be a consistent set of functions a provider must implement
100 See L<provider-keymgmt(7)> for further details.
104 OSSL_FUNC_kem_newctx() should create and return a pointer to a provider side
108 The parameter I<provctx> is the provider context generated during provider
109 initialisation (see L<provider(7)>).
[all …]
H A Dcrypto.pod47 A provider in OpenSSL is a component that collects together algorithm
49 provider loaded that contains an implementation of it. OpenSSL comes with a
51 don't load a provider explicitly (either in program code or via config) then the
52 OpenSSL built-in "default" provider will be automatically loaded.
57 options take effect. When a provider is loaded, it is only loaded within the
114 "provider=default" could be used to force the selection to only consider
115 algorithm implementations in the default provider.
129 Users of the OpenSSL libraries never query a provider directly for an algorithm
149 no provider has been loaded in this library context then the default provider
195 Fetch the operation type implementation from any provider given a library
[all …]
H A Dfips_module.pod105 also activates the "base" provider. The base provider does not include any
133 that are available in the default OpenSSL Provider.
166 Applications may choose to load the FIPS provider explicitly rather than relying
169 in this case we do not automatically activate the FIPS provider via that config
178 FIPS provider can then be loaded programmatically like this:
180 #include <openssl/provider.h>
189 printf("Failed to load FIPS provider\n");
195 printf("Failed to load base provider\n");
208 cryptographic functions before this occurs then, if no provider has yet been
209 loaded, then the default provider will be automatically loaded. If you then
[all …]
H A Dprovider-asym_cipher.pod5 provider-asym_cipher - The asym_cipher library E<lt>-E<gt> provider functions
47 This documentation is primarily aimed at provider authors. See L<provider(7)>
57 F<libcrypto> and the provider in L<OSSL_DISPATCH(3)> arrays via
58 L<OSSL_ALGORITHM(3)> arrays that are returned by the provider's
60 (see L<provider-base(7)/Provider Functions>).
92 In order to be a consistent set of functions a provider must implement
104 See L<provider-keymgmt(7)> for further details.
108 OSSL_FUNC_asym_cipher_newctx() should create and return a pointer to a provider side
112 The parameter I<provctx> is the provider context generated during provider
113 initialisation (see L<provider(7)>).
[all …]
/freebsd/secure/lib/libcrypto/man/man3/
H A DOSSL_PROVIDER.3148 \&\- provider routines
152 \& #include <openssl/provider.h>
165 \& int (*cb)(OSSL_PROVIDER *provider, void *cbdata),
194 implementation providers (see \fBprovider\fR\|(7) for information on what a
195 provider is).
196 A provider can be built in to the application or the OpenSSL
209 \&\fBOSSL_PROVIDER_add_builtin()\fR is used to add a built in provider to
211 provider name with a provider initialization function.
214 \&\fBOSSL_PROVIDER_load()\fR loads and initializes a provider.
215 This may simply initialize a provider that was previously added with
[all …]
/freebsd/release/
H A DMakefile.vagrant66 .for PROVIDER in ${VAGRANT_PROVIDERS}
67 CLEANFILES+= vagrant-do-package-${PROVIDER} ${VAGRANT_TARGET}.${PROVIDER}.box
68 CLEANDIRS+= ${PROVIDER}
69 VAGRANT_UPLOAD_TGTS+= vagrant-do-upload-${PROVIDER}
71 ${PROVIDER}:
72 @mkdir -p ${PROVIDER}
74 ${VAGRANT_TARGET}.${PROVIDER}.box: ${PROVIDER} cw-vagrant-${PROVIDER} vagran
[all...]
/freebsd/tools/regression/geom/ConfCmp/
H A Da1.conf14 <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 Da1a.conf14 <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 Da1d.conf14 <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 Da1b.conf14 <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 Da1c.conf14 <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 Dprovider-base.7133 .IX Title "PROVIDER-BASE 7ossl"
134 .TH PROVIDER-BASE 7ossl "2023-09-19" "3.0.11" "OpenSSL"
140 provider\-base
141 \&\- The basic OpenSSL library <\-> provider functions
224 \& int (*create_cb)(const OSSL_CORE_HANDLE *provider,
226 \& int (*remove_cb)(const OSSL_CORE_HANDLE *provider,
237 \& /* Functions offered by the provider to libcrypto */
254 \&\fIlibcrypto\fR and the provider in \s-1\fBOSSL_DISPATCH\s0\fR\|(3) arrays, in the call
255 of the provider initialization function. See \*(L"Provider\*(R" in \fBprovider\fR\|(7)
275 provider):
[all …]
H A Dcrypto.7177 A provider in OpenSSL is a component that collects together algorithm
179 provider loaded that contains an implementation of it. OpenSSL comes with a
181 don't load a provider explicitly (either in program code or via config) then the
182 OpenSSL built-in \*(L"default\*(R" provider will be automatically loaded.
186 options take effect. When a provider is loaded, it is only loaded within the
240 \&\*(L"provider=default\*(R" could be used to force the selection to only consider
241 algorithm implementations in the default provider.
254 Users of the OpenSSL libraries never query a provider directly for an algorithm
271 no provider has been loaded in this library context then the default provider
308 Fetch the operation type implementation from any provider given a library
[all …]
H A Dprovider.7133 .IX Title "PROVIDER 7ossl"
134 .TH PROVIDER 7ossl "2023-09-19" "3.0.11" "OpenSSL"
140 provider \- OpenSSL operation implementation providers
143 #include <openssl/provider.h>
148 This page contains information useful to provider authors.
150 A \fIprovider\fR, in OpenSSL terms, is a unit of code that provides one
164 .SS "Provider"
165 .IX Subsection "Provider"
166 A \fIprovider\fR offers an initialization function, as a set of base
183 \&\fIhandle\fR is the OpenSSL library object for the provider, and works
[all …]
/freebsd/sys/contrib/openzfs/module/icp/core/
H A Dkcf_prov_tabs.c34 * The provider table is indexed by crypto_provider_id_t. Each
35 * element of the table contains a pointer to a provider descriptor,
39 * provider descriptors.
52 * a crypto provider registers with kcf. The provider calls the
56 * A provider unregisters by calling crypto_unregister_provider()
84 * Add a provider to the provider table. If no free entry can be found
85 * for the new provider, returns CRYPTO_HOST_MEMORY. Otherwise, add
86 * the provider to the table, initialize the pd_prov_id field
87 * of the specified provider descriptor to the index in that table,
89 * provider when pointed to by a table entry.
[all …]
/freebsd/contrib/llvm-project/lldb/source/Plugins/Language/ObjC/
H A DObjCLanguage.cpp259 "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/test/recipes/
H A D30-test_evp_fetch_prov.t31 { 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/crypto/openssl/doc/internal/man7/
H A DEVP_PKEY.pod24 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 operation
[all...]

12345678910>>...53