| /freebsd/share/man/man5/ |
| H A D | src.conf.5 | 187 is set explicitly)
191 is set explicitly)
195 is set explicitly)
199 is set explicitly)
242 is set explicitly)
246 is set explicitly)
275 is set explicitly)
279 is set explicitly)
413 is set explicitly)
417 is set explicitly)
[all …]
|
| /freebsd/contrib/llvm-project/llvm/include/llvm/IR/ |
| H A D | Analysis.h | 87 /// otherwise only a short list of analyses that have been explicitly updated
100 /// preserved if it's not abandoned, and (a) it's explicitly marked as
167 /// by some other set or was previously explicitly marked as preserved.
179 /// by some other set or was previously explicitly marked as preserved.
200 // The intersection requires the *union* of the explicitly not-preserved in intersect()
221 // The intersection requires the *union* of the explicitly not-preserved in intersect()
248 /// - the analysis is explicitly preserved or
256 /// explicitly invalidated. Even if the analysis is not explicitly
261 /// - \p AnalysisSetT is explicitly preserved or
299 /// This is only true when no analyses have been explicitly abandoned.
[all …]
|
| /freebsd/crypto/openssl/doc/designs/ |
| H A D | fetching-composite-algorithms.md | 7 We currently support - at least in the public libcrypto API - explicitly
13 explicitly fetched algorithms is lacking: asymmetric algorithms.
49 - [Functions for explicitly fetched signature algorithms]
50 - [Functions for explicitly fetched asym-cipher algorithms] (not yet designed)
51 - [Functions for explicitly fetched keyexch algorithms] (not yet designed)
134 [Functions for explicitly fetched signature algorithms]:
135 functions-for-explicitly-fetched-signature-algorithms.md
|
| H A D | functions-for-explicitly-fetched-signature-algorithms.md | 1 Functions for explicitly fetched PKEY algorithms
8 basic need, explicitly fetched signature algorithms. The following method
20 They can be extended to accept an explicitly fetched algorithm of the right
133 the use of an explicitly fetched implementation of a composite algorithm
187 an explicitly fetched `EVP_SIGNATURE` argument (they can at least be used
189 is possible to use with the explicitly fetched algorithm, the following
|
| /freebsd/secure/lib/libcrypto/man/man7/ |
| H A D | openssl-quic-concurrency.7 | 80 A QUIC domain is instantiated either explicitly (\fBSSL_new_domain\fR\|(3)) or
89 explicitly create a QUIC domain SSL object and never directly references the
96 Regardless of whether a QUIC domain is explicitly created, the internal
165 optional and may need to be explicitly requested by an application depending on
178 default concurrency model if the application does not explicitly specify a
187 explicitly select the SCM concurrency model.
191 concurrency model and b) explicitly opt in or out of blocking I/O support
201 Applications should explicitly configure a concurrency model during
268 If an explicit QUIC domain is not explicitly created using \fBSSL_new_domain\fR\|(3),
306 blocking mode can be changed explicitly using \fBSSL_set_blocking_mode\fR\|(3).
|
| H A D | ossl-guide-libraries-introduction.7 | 110 If you don\*(Aqt load a provider explicitly (either in program code or via config)
128 If an application does not explicitly create a library context then the
158 Property query strings can be specified explicitly as an argument to a function.
246 automatically loaded. If you explicitly load any provider then the "default"
247 provider would also need to be explicitly loaded if it is required.
266 be loaded explicitly, either in code or through OpenSSL configuration
283 be loaded explicitly, either in code or through OpenSSL configuration
295 be automatically loaded if no other provider has been explicitly loaded. To
296 prevent that from happening you can explicitly load the null provider.
|
| /freebsd/crypto/openssl/doc/man7/ |
| H A D | openssl-quic-concurrency.pod | 20 A QUIC domain is instantiated either explicitly (L<SSL_new_domain(3)>) or
35 explicitly create a QUIC domain SSL object and never directly references the
44 Regardless of whether a QUIC domain is explicitly created, the internal
135 optional and may need to be explicitly requested by an application depending on
149 default concurrency model if the application does not explicitly specify a
163 explicitly select the SCM concurrency model.
169 concurrency model and b) explicitly opt in or out of blocking I/O support
181 Applications should explicitly configure a concurrency model during
274 If an explicit QUIC domain is not explicitly created using L<SSL_new_domain(3)>,
322 blocking mode can be changed explicitly using L<SSL_set_blocking_mode(3)>.
|
| H A D | ossl-guide-libraries-introduction.pod | 50 If you don't load a provider explicitly (either in program code or via config)
69 If an application does not explicitly create a library context then the
100 Property query strings can be specified explicitly as an argument to a function.
192 automatically loaded. If you explicitly load any provider then the "default"
193 provider would also need to be explicitly loaded if it is required.
214 be loaded explicitly, either in code or through OpenSSL configuration
232 be loaded explicitly, either in code or through OpenSSL configuration
245 be automatically loaded if no other provider has been explicitly loaded. To
246 prevent that from happening you can explicitly load the null provider.
|
| /freebsd/crypto/openssl/doc/man3/ |
| H A D | SSL_CTX_get_verify_mode.pod | 27 in B<ctx>. If no limit has been explicitly set, -1 is returned and the
31 in B<ssl>. If no limit has been explicitly set, -1 is returned and the
35 callback currently set in B<ctx>. If no callback was explicitly set, the
39 callback currently set in B<ssl>. If no callback was explicitly set, the
|
| H A D | SSL_set_connect_state.pod | 38 requested, the handshake routines must be explicitly set.
44 the handshake routines must be explicitly set in advance using either
48 SSL_set_accept_state() is called (either automatically or explicitly),
|
| /freebsd/contrib/bearssl/src/ |
| H A D | config.h | 120 * If the getentropy() call fails, and BR_USE_URANDOM is not explicitly
178 * Note: if BR_LOMUL is not explicitly enabled or disabled, then
187 * enabled explicitly, then that AES implementation will be compiled only
188 * if a compatible compiler is detected. If set explicitly to 0, the
197 * is not enabled explicitly, then support for SSE2 intrinsics will be
198 * automatically detected. If set explicitly to 0, then SSE2 code will
207 * If this is not enabled explicitly, then that implementation will be
|
| /freebsd/crypto/openssl/ |
| H A D | README-PROVIDERS.md | 30 explicitly (e.g. in the application or via config), then this is the provider
35 providers, then you must load it explicitly.
49 legacy provider explicitly.
113 Note that once you have explicitly loaded a provider into the library context
115 often also want to explicitly load the default provider, as is done here:
|
| /freebsd/secure/lib/libcrypto/man/man3/ |
| H A D | SSL_CTX_get_verify_mode.3 | 89 in \fBctx\fR. If no limit has been explicitly set, \-1 is returned and the
93 in \fBssl\fR. If no limit has been explicitly set, \-1 is returned and the
97 callback currently set in \fBctx\fR. If no callback was explicitly set, the
101 callback currently set in \fBssl\fR. If no callback was explicitly set, the
|
| H A D | SSL_set_connect_state.3 | 99 requested, the handshake routines must be explicitly set.
105 the handshake routines must be explicitly set in advance using either
109 \&\fBSSL_set_accept_state()\fR is called (either automatically or explicitly),
|
| /freebsd/share/man/man4/ |
| H A D | mac_portacl.4 | 85 policy only affects ports explicitly bound by a user process (either
92 connections where the process has not explicitly selected a port:
104 controlled ports will fail if not explicitly allowed by the port
181 explicitly allow this.
|
| /freebsd/crypto/openssl/providers/common/include/prov/ |
| H A D | provider_util.h | 17 * explicitly fetched cipher.
29 * the digest, always. |alloc_md| only holds a reference to an explicitly
117 * As an option, a MAC name may be explicitly given, and if it is, the "mac"
119 * Similarly, as an option, a cipher name or a digest name may be explicitly
|
| /freebsd/crypto/openssl/test/ |
| H A D | README-external.md | 57 explicitly run (with more debugging):
86 explicitly run (with more debugging):
109 explicitly run (with more debugging):
139 explicitly run (with more debugging):
|
| /freebsd/contrib/netbsd-tests/share/mk/ |
| H A D | t_test.sh | 66 atf_tc_fail("Failing explicitly");
85 fail("Failing explicitly");
101 atf_fail "Failing explicitly"
|
| /freebsd/bin/test/tests/ |
| H A D | Makefile | 5 # root. Explicitly tell Kyua to drop privileges.
7 # TODO(jmmv): Kyua needs to do this by default, not only when explicitly
|
| /freebsd/contrib/llvm-project/llvm/lib/ObjCopy/wasm/ |
| H A D | WasmObjcopy.cpp | 63 // Explicitly-requested sections. in removeSections()
85 // Keep debug sections, unless explicitly requested to remove. in removeSections()
93 // Explicitly keep these sections regardless of previous removes. in removeSections()
101 // Explicitly keep these sections regardless of previous removes. in removeSections()
|
| /freebsd/contrib/llvm-project/lldb/bindings/interface/ |
| H A D | SBProgressDocstrings.i | 13 completed update is reported even if the user doesn't explicitly cause one
52 # Explicitly send a progressEnd, otherwise this will be sent
66 happens automatically when the SBProcess object is destroyed, but can be done explicitly
|
| /freebsd/tests/sys/geom/class/multipath/ |
| H A D | misc.sh | 244 # Explicitly prefer the final path
269 # Explicitly fail the first path
273 # Explicitly restore it
300 # Explicitly fail the first path
334 # Explicitly rotate the paths
|
| /freebsd/contrib/bearssl/inc/ |
| H A D | bearssl.h | 83 * explicitly authorised by the documentation. As an exception, when
87 * not explicitly allowed.
111 * Except when explicitly indicated, structure contents are opaque: they
150 * names. Some of the options can be explicitly set in the internal
|
| /freebsd/sys/dev/bhnd/cores/pci/ |
| H A D | bhnd_pci_hostbvar.h | 91 * PCI-PM power management must be explicitly enabled via
111 * explicitly set (to 114ns) to fix slow L1->L0 transition issues.
126 * flag; if set, ASPM and CLKREQ should be explicitly disabled. If not
127 * set, they should be explicitly enabled.
|
| /freebsd/contrib/llvm-project/llvm/include/llvm/Transforms/Vectorize/ |
| H A D | LoopVectorize.h | 87 /// If true, only loops that explicitly request interleaving are considered.
91 /// If true, only loops that explicitly request vectorization are considered.
134 /// If true, only loops that explicitly request interleaving are considered.
138 /// If true, only loops that explicitly request vectorization are considered.
|