| /freebsd/lib/libc/posix1e/ |
| H A D | mac.3 | 153 These APIs are loosely based on the APIs described in POSIX.1e, as described
155 However, the resemblance of these APIs to the POSIX APIs is loose, as the
156 POSIX APIs were unable to express some notions required for flexible and
|
| /freebsd/secure/lib/libcrypto/man/man7/ |
| H A D | migration_guide.7 | 185 \&\*(L"high level\*(R" APIs (for example those functions prefixed with \f(CW\*(C`EVP\*(C'\fR). They…
186 be accessed using the \*(L"Low Level APIs\*(R".
209 \fILow Level APIs\fR
210 .IX Subsection "Low Level APIs"
212 OpenSSL has historically provided two sets of APIs for invoking cryptographic
213 algorithms: the \*(L"high level\*(R" APIs (such as the \f(CW\*(C`EVP\*(C'\fR APIs) and the \*(L"low…
214 APIs. The high level APIs are typically designed to work across all algorithm
215 types. The \*(L"low level\*(R" APIs are targeted at a specific algorithm implementation.
216 For example, the \s-1EVP\s0 APIs provide the functions \fBEVP_EncryptInit_ex\fR\|(3),
219 On the other hand, to do \s-1AES\s0 encryption using the low level APIs you would have
[all …]
|
| H A D | fips_module.7 | 157 legacy APIs or features that avoid the \s-1FIPS\s0 module. Specifically this includes:
159 Low level cryptographic APIs (use the high level APIs, such as \s-1EVP,\s0 instead)
167 All of the above APIs are deprecated in OpenSSL 3.0 \- so a simple rule is to
258 Usage of certain deprecated APIs avoids the use of the \s-1FIPS\s0 module.
260 If any applications use those APIs then the \s-1FIPS\s0 module will not be used.
519 this will be invisible to you if you are using APIs that existed in
|
| /freebsd/crypto/openssl/ssl/ |
| H A D | tls_depr.c | 10 /* We need to use some engine and HMAC deprecated APIs */
17 * Engine APIs are only used to support applications that still use ENGINEs.
93 * The HMAC APIs below are only used to support the deprecated public API
148 /* Some deprecated public APIs pass DH objects */
167 /* Some deprecated public APIs pass EC_KEY objects */
|
| /freebsd/contrib/libpcap/pcap/ |
| H A D | socket.h | 61 * On Windows, this shouldn't break any APIs, as any code using
62 * the two active-mode APIs that return a socket handle would
94 * active-mode APIs that return a socket handle if those programs
95 * were written to assign the return values of those APIs to a
97 * those APIs are only provided if libpcap is built with remote
|
| H A D | funcattrs.h | 152 * APIs to be designated as "first available in this release" to do so
155 * On macOS, Apple can tweak this to make various APIs "weakly exported
158 * new APIs when available. (Yes, such third-party software exists -
161 * come with a version compiled to use the APIs present in that release.)
164 * and installing libpcap on macOS yourself, the APIs will be available
201 * The remote capture APIs are, in 1.9 and 1.10, usually only
|
| /freebsd/sys/contrib/openzfs/config/ |
| H A D | kernel-idmap_mnt_api.m4 | 4 dnl # Check if APIs for idmapped mount are available
16 AC_MSG_CHECKING([whether APIs for idmapped mount are present])
20 [APIs for idmapped mount are present])
|
| /freebsd/crypto/openssl/doc/man7/ |
| H A D | migration_guide.pod | 50 "high level" APIs (for example those functions prefixed with C<EVP>). They cannot
51 be accessed using the L</Low Level APIs>.
74 =head3 Low Level APIs
76 OpenSSL has historically provided two sets of APIs for invoking cryptographic
77 algorithms: the "high level" APIs (such as the C<EVP> APIs) and the "low level"
78 APIs. The high level APIs are typically designed to work across all algorithm
79 types. The "low level" APIs are targeted at a specific algorithm implementation.
80 For example, the EVP APIs provid
[all...] |
| H A D | fips_module.pod | 24 legacy APIs or features that avoid the FIPS module. Specifically this includes:
30 Low level cryptographic APIs (use the high level APIs, such as EVP, instead)
44 All of the above APIs are deprecated in OpenSSL 3.0 - so a simple rule is to
140 Usage of certain deprecated APIs avoids the use of the FIPS module.
142 If any applications use those APIs then the FIPS module will not be used.
394 this will be invisible to you if you are using APIs that existed in
|
| /freebsd/lib/libc/locale/ |
| H A D | DESIGN.xlocale | 5 The xlocale APIs come from Darwin, although a subset is now part of POSIX 2008.
11 This document describes the implementation of these APIs for FreeBSD.
112 parameter. The old APIs are then reimplemented with a call to `__get_locale()`
114 APIs, but also simplifies the modifications to these functions. The
123 Differences to Darwin APIs
|
| /freebsd/contrib/llvm-project/llvm/include/llvm/Analysis/ |
| H A D | GenericDomTreeUpdater.h | 109 /// \name Mutation APIs
111 /// These methods provide APIs for submitting updates to the DomTreeT and
119 /// explicitly call Flush APIs. It is recommended to use this update strategy
127 /// it is not encouraged to use these APIs directly.
177 /// \name Flush APIs
179 /// CAUTION! By the moment these flush APIs are called, the current CFG needs
|
| H A D | DomTreeUpdater.h | 44 /// \name Mutation APIs
46 /// These methods provide APIs for submitting updates to the DominatorTree and
54 /// explicitly call Flush APIs. It is recommended to use this update strategy
62 /// it is not encouraged to use these APIs directly.
|
| /freebsd/contrib/ntp/sntp/libevent/ |
| H A D | whatsnew-2.0.txt | 17 growing pile of APIs. As of this writing, it covers everything except the
21 2. New and Improved Event APIs
23 Many APIs are improved, refactored, or deprecated in Libevent 2.0.
29 or if you want to port old code, we strongly recommend using the new APIs
30 and avoiding deprecated APIs as much as possible.
78 2.2. New thread-safe, binary-compatible, harder-to-mess-up APIs
82 to no longer build with another. The problems with now-deprecated APIs
184 All APIs that formerly accepted int as a socket type now accept
576 The evhttp uriencoding and uridecoding APIs have updated versions
|
| /freebsd/contrib/libevent/ |
| H A D | whatsnew-2.0.txt | 17 growing pile of APIs. As of this writing, it covers everything except the
21 2. New and Improved Event APIs
23 Many APIs are improved, refactored, or deprecated in Libevent 2.0.
29 or if you want to port old code, we strongly recommend using the new APIs
30 and avoiding deprecated APIs as much as possible.
78 2.2. New thread-safe, binary-compatible, harder-to-mess-up APIs
82 to no longer build with another. The problems with now-deprecated APIs
184 All APIs that formerly accepted int as a socket type now accept
576 The evhttp uriencoding and uridecoding APIs have updated versions
|
| /freebsd/crypto/openssl/include/internal/ |
| H A D | deprecated.h | 11 * This header file should be included by internal code that needs to use APIs
14 * low level APIs that are otherwise deprecated.
|
| /freebsd/contrib/llvm-project/lldb/bindings/interface/ |
| H A D | SBCommandInterpreterDocstrings.i | 9 '''Test the SBCommandInterpreter APIs.'''
20 # Exercise some APIs....
|
| /freebsd/contrib/elftoolchain/libelf/ |
| H A D | elf_begin.3 | 43 archives for further processing by other APIs in the
52 APIs.
236 \&... create the ELF image using other elf(3) APIs ...
|
| H A D | gelf.3 | 112 APIs to indicate to the ELF library that an ELF data structure is dirty.
126 .Ss GElf Programming APIs
127 This section provides an overview of the GElf programming APIs.
|
| /freebsd/share/man/man3/ |
| H A D | qmath.3 | 39 data types and APIs support fixed-point math based on the
42 The APIs have been built around the following data types:
193 data types and APIs support fixed-point math based on the
206 The APIs have been built around the following q_t derived data types:
|
| /freebsd/sys/contrib/openzfs/ |
| H A D | RELEASES.md | 13 user space library APIs (libzfs.so). Existing user/kernel interfaces are
19 The user space library APIs and user/kernel interface are considered to
|
| /freebsd/sys/contrib/device-tree/Bindings/firmware/xilinx/ |
| H A D | xlnx,zynqmp-firmware.txt | 7 driver provides an interface to firmware APIs. Interface APIs can be
|
| /freebsd/sys/contrib/openzfs/include/sys/ |
| H A D | skein.h | 90 /* Skein APIs for (incremental) "straight hashing" */
107 * Skein APIs for "extended" initialization: MAC keys, tree hashing.
128 * Skein APIs for MAC and tree hash:
|
| /freebsd/contrib/openbsm/ |
| H A D | NEWS | 296 - Add APIs au_poltostr() and au_strtopol() to convert between text
323 for almost all existing constants and APIs.
325 APIs, pass in the audit filter daemon state pointer, which is then used by
327 future service APIs provided by the filter daemon to maintain their own
375 the APIs that invoke gettimeofday(), rather than having a variable
383 - Universally, APIs now assume that IP addresses and ports are provided
384 in network byte order. APIs now generally provide these types in
488 documentation of private APIs, and bug fixes.
|
| /freebsd/contrib/openbsm/bin/auditfilterd/ |
| H A D | auditfilterd.8 | 79 daemon and audit filter APIs were created by
84 APIs and services it offers can and will change in future OpenBSM releases.
|
| /freebsd/sys/dev/vmm/ |
| H A D | vmm_mem.h | 48 * APIs that modify the guest memory map require all vcpus to be frozen.
62 * APIs that inspect the guest memory map require only a *single* vcpu to
|