| /freebsd-src/share/man/man7/ |
| H A D | clocks.7 | 47 It is not available to applications.
51 It is not directly available to applications.
108 Applications should determine its actual frequency using
115 It is not available to applications.
121 and is exported to applications in
129 applications.
135 It is not available to applications.
154 It is not available to applications.
|
| /freebsd-src/secure/lib/libcrypto/man/man7/ |
| H A D | migration_guide.7 | 161 of applications will work unchanged with OpenSSL 3.0 if those applications
164 applications need to take advantage of some of the new features available in
207 \&\*(L"Using the \s-1FIPS\s0 Module in applications\*(R".
225 your applications, but you may start to see deprecation warnings during
241 Applications using the \s-1EVP\s0 APIs to access these algorithms should instead use
242 more modern algorithms. If that is not possible then these applications
257 This is particularly relevant for applications written to use the OpenSSL 3.0
317 Existing applications that use \s-1KDF\s0 algorithms using \s-1EVP_PKEY\s0
320 All new applications should use the new \s-1\fBEVP_KDF\s0\fR\|(3) interface.
333 All new applications should use the new \s-1\fBEVP_MAC\s0\fR\|(3) interface.
[all …]
|
| H A D | fips_module.7 | 156 Applications written to use the OpenSSL 3.0 \s-1FIPS\s0 module should not use any
170 .SS "Making all applications use the \s-1FIPS\s0 module by default"
171 .IX Subsection "Making all applications use the FIPS module by default"
172 One simple approach is to cause all applications that are using OpenSSL to only
175 This approach can be done purely via configuration. As long as applications are
230 Any applications that use OpenSSL 3.0 and are started after these changes are
231 made will start using only the \s-1FIPS\s0 module unless those applications take
239 are required in applications in order to benefit from the \s-1FIPS\s0 module. There are
242 You may not want all applications to use the \s-1FIPS\s0 module.
244 It may be the case that some applications should and some should not use the
[all …]
|
| /freebsd-src/sys/contrib/device-tree/Bindings/iio/temperature/ |
| H A D | melexis,mlx90632.yaml | 15 There are various applications for the Infra Red contactless temperature
16 sensor and MLX90632 is most suitable for consumer applications where
19 object temperature range for industrial applications. Since it can
32 MLX90635 is most suitable for consumer applications where
35 object temperature range for industrial applications, while just 0.2
36 degree Celsius for human body measurement applications. Since it can
|
| H A D | mlx90632.txt | 5 There are various applications for the Infra Red contactless temperature sensor
6 and MLX90632 is most suitable for consumer applications where measured object
9 industrial applications. Since it can operate and measure ambient temperature
|
| /freebsd-src/crypto/openssl/ |
| H A D | README-ENGINES.md | 58 applications when they use that ENGINE. Work is in progress (or at least
60 NCONF) code so that applications using OpenSSL's existing configuration
62 Presently however, applications must use the ENGINE API itself to provide
86 devices from common OpenSSL-based applications. Bugs and/or inexplicable
119 This way, applications do not need to know anything specific to any
135 applications. This could be because existing compiled-in implementations
141 The other use-case for "dynamic" is with applications that wish to
147 applications based on OpenSSL 0.9.7 or later. If you're using an
180 ENGINE's "id". For most applications, this isn't necessary - but some
216 Applications that support the ENGINE API and more specifically, the
[all …]
|
| /freebsd-src/crypto/openssl/doc/man7/ |
| H A D | fips_module.pod | 23 Applications written to use the OpenSSL 3.0 FIPS module should not use any
48 =head2 Making all applications use the FIPS module by default
50 One simple approach is to cause all applications that are using OpenSSL to only
53 This approach can be done purely via configuration. As long as applications are
102 Any applications that use OpenSSL 3.0 and are started after these changes are
103 made will start using only the FIPS module unless those applications take
111 are required in applications in order to benefit from the FIPS module. There are
118 You may not want all applications to use the FIPS module.
120 It may be the case that some applications should and some should not use the
125 If applications take explicit steps to not load the default config file or
[all …]
|
| H A D | migration_guide.pod | 28 of applications will work unchanged with OpenSSL 3.0 if those applications
31 applications need to take advantage of some of the new features available in
72 L</Using the FIPS Module in applications>.
89 your applications, but you may start to see deprecation warnings during
104 Applications using the EVP APIs to access these algorithms should instead use
105 more modern algorithms. If that is not possible then these applications
119 This is particularly relevant for applications written to use the OpenSSL 3.0
181 Existing applications that use KDF algorithms using EVP_PKEY
184 All new applications should use the new L<EVP_KDF(3)> interface.
196 All new applications should use the new L<EVP_MAC(3)> interface.
[all …]
|
| /freebsd-src/contrib/ofed/librdmacm/man/ |
| H A D | rsocket.7.in | 11 for applications. Rsocket APIs are intended to match the behavior
109 applications which must mix rsocket fd's with standard socket fd's or
113 Existing applications can make use of rsockets through the use of a
122 Note that not all applications will work with rsockets. Support is
125 the preload library for applications that call fork, users must
128 supportable for server applications that accept a connection, then
156 Applications can override default values programmatically through the
|
| /freebsd-src/crypto/openssl/doc/man3/ |
| H A D | EVP_PKEY_set1_RSA.pod | 81 functions are deprecated. Applications should instead use
88 I<pkey> is freed. These macros are deprecated. Applications should instead read
96 These functions are deprecated. Applications should instead use the EVP_PKEY
98 then applications should use L<EVP_PKEY_get_params(3)> and other similar
107 are deprecated. Applications should instead use the EVP_PKEY directly where
109 applications should use L<EVP_PKEY_get_params(3)> and other similar functions.
130 function is deprecated. Applications should use providers instead of engines
136 error occurs. This function is deprecated. Applications should use providers
159 in order that applications can "free" the return value. However applications
176 Most applications wishing to know a key type will simply call
|
| H A D | SSL_CTX_set_tmp_dh_callback.pod | 58 Typically applications should use well known DH parameters that have built-in
70 Applications may supply their own DH parameters instead of using the built-in
71 values. This approach is discouraged and applications should in preference use
72 the built-in parameter support described above. Applications wishing to supply
83 ownership of the B<DH> object is retained by the application. Applications
90 functions are deprecated. Applications should instead use "auto" parameters, or
|
| H A D | MD5.pod | 50 Applications should instead use L<EVP_DigestInit_ex(3)>, L<EVP_DigestUpdate(3)>
75 Applications should use the higher level functions
82 applications. In new applications, hashes from the SHA-2 or SHA-3 family
|
| /freebsd-src/crypto/heimdal/lib/wind/ |
| H A D | rfc3490.txt | 16 Internationalizing Domain Names in Applications (IDNA)
35 Internationalizing Domain Names in Applications (IDNA) for handling
68 6. Implications for typical applications using DNS............... 13
69 6.1 Entry and display in applications......................... 14
70 6.2 Applications and resolver libraries....................... 15
86 IDNA works by allowing applications to use certain ASCII name labels
94 This document does not require any applications to conform to IDNA,
95 but applications can elect to use IDNA in order to support IDN while
105 the IDN Working Group would depend on user applications, resolvers,
109 applications only; no changes are needed to the DNS protocol or any
[all …]
|
| /freebsd-src/secure/lib/libcrypto/man/man3/ |
| H A D | EVP_PKEY_set1_RSA.3 | 218 functions are deprecated. Applications should instead use
225 \&\fIpkey\fR is freed. These macros are deprecated. Applications should instead read
233 These functions are deprecated. Applications should instead use the \s-1EVP_PKEY\s0
235 then applications should use \fBEVP_PKEY_get_params\fR\|(3) and other similar
244 are deprecated. Applications should instead use the \s-1EVP_PKEY\s0 directly where
246 applications should use \fBEVP_PKEY_get_params\fR\|(3) and other similar functions.
267 function is deprecated. Applications should use providers instead of engines
273 error occurs. This function is deprecated. Applications should use providers
295 in order that applications can \*(L"free\*(R" the return value. However applications
311 Most applications wishing to know a key type will simply call
|
| H A D | SSL_CTX_set_tmp_dh_callback.3 | 195 Typically applications should use well know \s-1DH\s0 parameters that have built-in
207 Applications may supply their own \s-1DH\s0 parameters instead of using the built-in
208 values. This approach is discouraged and applications should in preference use
209 the built-in parameter support described above. Applications wishing to supply
220 ownership of the \fB\s-1DH\s0\fR object is retained by the application. Applications
227 functions are deprecated. Applications should instead use \*(L"auto\*(R" parameters, or
|
| /freebsd-src/contrib/ofed/libmlx5/ |
| H A D | mlx5dv.7 | 14 of user applications portability it has a performance penalty. For some
15 applications optimizing performance is more important than portability.
17 The mlx5 direct verbs API is intended for such applications.
35 thus using the mlx5 direct verbs does not limit the applications
|
| /freebsd-src/contrib/libpcap/doc/ |
| H A D | README.linux | 11 will probably be used by other applications in the future) won't work
20 can replace that older version without breaking applications built with
22 procedure for applications whose configure script doesn't use the
24 procedure for applications whose configure scripts use the pcap-config
|
| /freebsd-src/share/man/man4/ |
| H A D | vmci.4 | 32 User level applications in a virtual machine can use VMCI through vSockets
39 applications, where network access of the virtual machine is restricted
42 hardware running as host applications and automated testing of applications
|
| H A D | auditpipe.4 | 41 unwieldy for live monitoring applications such as host-based intrusion
44 without notice to applications that may be accessing the file.
46 The audit facility provides an audit pipe facility for applications requiring
72 Applications may choose to track the global audit trail, or configure local
109 This allows applications to track events not captured in the global audit
254 allow applications to select which records are dropped, possibly in the style
|
| /freebsd-src/lib/librss/ |
| H A D | librss.3 | 7 .Nd Provide Receive-side scaling awareness to userland applications
33 Applications will typically call
52 Applications will typically use the
63 Typically applications will wish to just query for
|
| /freebsd-src/lib/libc/posix1e/ |
| H A D | mac.conf.5 | 40 applications that operate on MAC labels.
70 The following example configures user applications to operate with
79 # Default label set to be used by simple MAC applications
94 In this example, userland applications will attempt to retrieve Biba,
|
| /freebsd-src/share/doc/papers/jail/ |
| H A D | mgt.ms | 27 accessible to host environment applications to use.
28 If the accessibility of some host applications in the jail environment is
29 not desirable, it is necessary to configure those applications to only
35 In this situation, it is sufficient to configure the networking applications
38 used by inetd and SSH, and disabling applications that are not capable
41 Other third party applications that have been installed on the host must also be
|
| /freebsd-src/lib/libc/gen/ |
| H A D | statvfs.3 | 53 statistics, but portable applications must not depend on this.
54 Applications must pass a pathname or file descriptor which refers to a
63 Applications should use
167 As standardized, portable applications cannot depend on these functions
|
| /freebsd-src/contrib/ncurses/ |
| H A D | INSTALL | 49 If you are trying to build applications using gpm with ncurses,
250 so you can use ncurses applications.
268 YOU MAY NOT BE ABLE TO COMPILE (OR RUN) NCURSES APPLICATIONS WITH C++.
288 which allows applications to specify what the default foreground and
289 background color are assumed to be. Most color applications use
310 built-in database, aka "fallback" entries. Embedded applications may
354 curses applications for memory leaks. To work around this, build a
409 Putting the header files into a subdirectory assumes that applications
423 almost all applications are designed to include a related set of
428 this, and breaks builds of portable applications. Likewise, putting
[all …]
|
| /freebsd-src/contrib/llvm-project/clang/include/clang/Tooling/ |
| H A D | Refactoring.h | 60 /// Replacement applications happen independently of the success of other
61 /// applications.
83 /// Replacement applications happen independently of the success of other
84 /// applications.
|