| /freebsd/secure/lib/libcrypto/man/man7/ |
| H A D | openssl-glossary.7 | 119 .IP "Explicit Fetching" 4
120 .IX Item "Explicit Fetching"
121 Explicit Fetching is a type of Fetching (see Fetching). Explicit Fetching is
124 .IP Fetching 4
125 .IX Item "Fetching"
126 Fetching is the process of looking through the available algorithm
130 Also see Explicit Fetching and Implicit Fetching.
139 .IP "Implicit Fetching" 4
140 .IX Item "Implicit Fetching"
141 Implicit Fetching is a type of Fetching (see Fetching). Implicit Fetching is
[all …]
|
| H A D | ossl-guide-libcrypto-introduction.7 | 100 .SH "ALGORITHM FETCHING"
101 .IX Header "ALGORITHM FETCHING"
103 Fetching is the process of looking through the available implementations,
107 Two types of fetching are supported by OpenSSL \- "Explicit fetching" and
108 "Implicit fetching".
109 .SS "Explicit fetching"
110 .IX Subsection "Explicit fetching"
111 Explicit fetching involves directly calling a specific API to fetch an algorithm
113 APIs. These explicit fetching functions usually have the name \f(CW\*(C`APINAME_fetch\*(C'\fR,
119 These fetching functions follow a fairly common pattern, where three
[all …]
|
| H A D | ossl-guide-libraries-introduction.7 | 141 See also "ALGORITHM FETCHING" in \fBossl\-guide\-libcrypto\-introduction\fR\|(7).
149 The process of selecting an algorithm implementation is known as "fetching".
163 See "ALGORITHM FETCHING" in \fBossl\-guide\-libcrypto\-introduction\fR\|(7) for more
164 information about fetching. See \fBproperty\fR\|(7) for more information about
227 algorithm identifier to the appropriate fetching function. Also see the provider
291 no algorithms in it at all. When fetching algorithms the default provider will
|
| /freebsd/crypto/openssl/doc/man7/ |
| H A D | openssl-glossary.pod | 72 =item Explicit Fetching
74 Explicit Fetching is a type of Fetching (see Fetching). Explicit Fetching is
78 =item Fetching
80 Fetching is the process of looking through the available algorithm
84 Also see Explicit Fetching and Implicit Fetching.
95 =item Implicit Fetching
97 Implicit Fetching is a type of Fetching (see Fetching). Implicit Fetching is
100 fetching an implementation is fetched automatically using default selection
191 Property Query Strings are used during fetching. See Fetching.
|
| H A D | ossl-guide-libcrypto-introduction.pod | 46 =head1 ALGORITHM FETCHING
49 Fetching is the process of looking through the available implementations,
53 Two types of fetching are supported by OpenSSL - L</Explicit fetching> and
54 L</Implicit fetching>.
56 =head2 Explicit fetching
58 Explicit fetching involves directly calling a specific API to fetch an algorithm
60 APIs. These explicit fetching functions usually have the name C<APINAME_fetch>,
66 These fetching functions follow a fairly common pattern, where three
76 L<OSSL_PROVIDER_load(3)>) will be considered by the fetching function. In case
82 For all currently implemented fetching functions this is the algorithm name.
[all …]
|
| H A D | OSSL_PROVIDER-base.pod | 23 It may be used in a property query string with fetching functions.
38 These may be used in a property query string with fetching functions to select
52 These may be used in a property query string with fetching functions to select
|
| H A D | ossl-guide-libraries-introduction.pod | 85 See also L<ossl-guide-libcrypto-introduction(7)/ALGORITHM FETCHING>.
94 The process of selecting an algorithm implementation is known as "fetching".
108 See L<ossl-guide-libcrypto-introduction(7)/ALGORITHM FETCHING> for more
109 information about fetching. See L<property(7)> for more information about
175 algorithm identifier to the appropriate fetching function. Also see the provider
244 no algorithms in it at all. When fetching algorithms the default provider will
|
| /freebsd/crypto/openssl/doc/designs/ |
| H A D | fetching-composite-algorithms.md | 1 Fetching composite algorithms and using them - adding the bits still missing
8 fetching composite algorithms (such as AES-128-CBC or HMAC-SHA256), and
79 numerical form). To enable this, explicit fetching is necessary.
83 As a matter of fact, we already have built-in support for fetching
86 fetched result, commonly known as support for explicit fetching.
117 the result of explicit fetching. So for example, while it's possible for a
122 support implicit fetching.
|
| /freebsd/sys/contrib/device-tree/Bindings/dma/ |
| H A D | arm-pl08x.txt | 15 - lli-bus-interface-ahb1: if AHB master 1 is eligible for fetching LLIs
16 - lli-bus-interface-ahb2: if AHB master 2 is eligible for fetching LLIs
17 - mem-bus-interface-ahb1: if AHB master 1 is eligible for fetching memory contents
18 - mem-bus-interface-ahb2: if AHB master 2 is eligible for fetching memory contents
|
| H A D | arm-pl08x.yaml | 57 description: if AHB master 1 is eligible for fetching LLIs
61 description: if AHB master 2 is eligible for fetching LLIs
65 description: if AHB master 1 is eligible for fetching memory contents
69 description: if AHB master 2 is eligible for fetching memory contents
|
| /freebsd/crypto/openssl/doc/man3/ |
| H A D | ASN1_item_d2i_bio.pod | 46 L<crypto(7)/ALGORITHM FETCHING> for more information about algorithm fetching.
59 string in I<propq>. See L<crypto(7)/ALGORITHM FETCHING> for more information
60 about algorithm fetching.
88 that the I<libctx> and I<propq> can be used when doing algorithm fetching.
|
| H A D | EVP_set_default_properties.pod | 22 L<crypto(7)/ALGORITHM FETCHING> for information about implicit and explicit
23 fetching.
51 that the context reference is valid and default fetching properties are not
|
| H A D | ASN1_EXTERN_FUNCS.pod | 146 for algorithm fetching in the I<propq> parameter. See
147 L<crypto(7)/ALGORITHM FETCHING> for further details. If I<asn1_ex_new_ex> is
154 for algorithm fetching in the I<propq> parameter. See
155 L<crypto(7)/ALGORITHM FETCHING> for further details. If I<asn1_ex_d2i_ex> is
|
| H A D | ASN1_item_new.pod | 22 L<crypto(7)/ALGORITHM FETCHING> for more information about algorithm fetching.
|
| H A D | X509_LOOKUP.pod | 99 query I<propq> are used when fetching algorithms from providers.
111 query I<propq> are used when fetching algorithms from providers.
129 query I<propq> are used when fetching algorithms from providers.
137 when fetching algorithms from providers.
|
| H A D | X509_STORE_add_cert.pod | 100 query I<propq> are used when fetching algorithms from providers.
112 property query I<propq> are used when fetching algorithms from providers.
130 fetching algorithms from providers.
|
| H A D | SMIME_read_ASN1.pod | 32 L<crypto(7)/ALGORITHM FETCHING> for further details about algorithm fetching.
|
| /freebsd/secure/lib/libcrypto/man/man3/ |
| H A D | ASN1_item_d2i_bio.3 | 105 "ALGORITHM FETCHING" in \fBcrypto\fR\|(7) for more information about algorithm fetching.
118 string in \fIpropq\fR. See "ALGORITHM FETCHING" in \fBcrypto\fR\|(7) for more information
119 about algorithm fetching.
147 that the \fIlibctx\fR and \fIpropq\fR can be used when doing algorithm fetching.
|
| H A D | EVP_set_default_properties.3 | 81 "ALGORITHM FETCHING" in \fBcrypto\fR\|(7) for information about implicit and explicit
82 fetching.
109 that the context reference is valid and default fetching properties are not
|
| H A D | ASN1_EXTERN_FUNCS.3 | 195 for algorithm fetching in the \fIpropq\fR parameter. See
196 "ALGORITHM FETCHING" in \fBcrypto\fR\|(7) for further details. If \fIasn1_ex_new_ex\fR is
202 for algorithm fetching in the \fIpropq\fR parameter. See
203 "ALGORITHM FETCHING" in \fBcrypto\fR\|(7) for further details. If \fIasn1_ex_d2i_ex\fR is
|
| H A D | X509_LOOKUP.3 | 158 query \fIpropq\fR are used when fetching algorithms from providers.
170 query \fIpropq\fR are used when fetching algorithms from providers.
188 query \fIpropq\fR are used when fetching algorithms from providers.
196 when fetching algorithms from providers.
|
| H A D | X509_STORE_add_cert.3 | 159 query \fIpropq\fR are used when fetching algorithms from providers.
171 property query \fIpropq\fR are used when fetching algorithms from providers.
189 fetching algorithms from providers.
|
| H A D | ASN1_item_new.3 | 81 "ALGORITHM FETCHING" in \fBcrypto\fR\|(7) for more information about algorithm fetching.
|
| /freebsd/usr.sbin/bsdinstall/distfetch/ |
| H A D | distfetch.c | 165 mgconf.title = "Fetching Distribution"; in fetch_files()
175 "Error (URL) while fetching %s: %s\n", urls[i], in fetch_files()
188 "Error (fopen) while fetching %s: %s\n", in fetch_files()
231 "Error (undone) while fetching %s: %s\n", in fetch_files()
235 "Error (libfetch) while fetching %s: %s\n", in fetch_files()
|
| /freebsd/lib/libpmc/pmu-events/arch/x86/silvermont/ |
| H A D | pipeline.json | 108 …rong (speculative) path must be discarded, and the processor must start fetching from the correct …
117 …rong (speculative) path must be discarded, and the processor must start fetching from the correct …
127 …rong (speculative) path must be discarded, and the processor must start fetching from the correct …
137 …rong (speculative) path must be discarded, and the processor must start fetching from the correct …
147 …rong (speculative) path must be discarded, and the processor must start fetching from the correct …
157 …rong (speculative) path must be discarded, and the processor must start fetching from the correct …
260 …o 2 broader parts: Front-end and Back-end. Front-end is responsible for fetching the instruction, …
|