| /freebsd/secure/lib/libcrypto/man/man7/ |
| H A D | ossl-guide-migration.7 | 1 .\" -*- mode: troff; coding: utf-8 -*-
19 .\" \*(C` and \*(C' are quotes in nroff, nothing in troff, for use with C<>.
29 .\" Escape single quotes in literal strings from groff's Unicode transform.
35 .\" entries marked with X<> in POD. Of course, you'll have to process the
36 .\" output yourself in some meaningful fashion.
57 .IX Title "OSSL-GUIDE-MIGRATION 7ossl"
58 .TH OSSL-GUIDE-MIGRATION 7ossl 2025-09-30 3.5.4 OpenSSL
60 .\" way too many mistakes in technical documents.
64 ossl\-guide\-migration, migration_guide
65 \&\- OpenSSL Guide: Migrating from older OpenSSL versions
[all …]
|
| H A D | evp.7 | 1 .\" -*- mode: troff; coding: utf-8 -*-
19 .\" \*(C` and \*(C' are quotes in nroff, nothing in troff, for use with C<>.
29 .\" Escape single quotes in literal strings from groff's Unicode transform.
35 .\" entries marked with X<> in POD. Of course, you'll have to process the
36 .\" output yourself in some meaningful fashion.
58 .TH EVP 7ossl 2025-09-30 3.5.4 OpenSSL
60 .\" way too many mistakes in technical documents.
64 evp \- high\-level cryptographic functions
72 The EVP library provides a high-level interface to cryptographic
73 functions.
[all …]
|
| H A D | provider-signature.7 | 1 .\" -*- mode: troff; coding: utf-8 -*-
19 .\" \*(C` and \*(C' are quotes in nroff, nothing in troff, for use with C<>.
29 .\" Escape single quotes in literal strings from groff's Unicode transform.
35 .\" entries marked with X<> in POD. Of course, you'll have to process the
36 .\" output yourself in some meaningful fashion.
57 .IX Title "PROVIDER-SIGNATURE 7ossl"
58 .TH PROVIDER-SIGNATURE 7ossl 2025-09-30 3.5.4 OpenSSL
60 .\" way too many mistakes in technical documents.
64 provider\-signature \- The signature library <\-> provider functions
72 \& * None of these are actual functions, but are displayed like this for
[all …]
|
| H A D | provider.7 | 1 .\" -*- mode: troff; coding: utf-8 -*-
19 .\" \*(C` and \*(C' are quotes in nroff, nothing in troff, for use with C<>.
29 .\" Escape single quotes in literal strings from groff's Unicode transform.
35 .\" entries marked with X<> in POD. Of course, you'll have to process the
36 .\" output yourself in some meaningful fashion.
58 .TH PROVIDER 7ossl 2025-09-30 3.5.4 OpenSSL
60 .\" way too many mistakes in technical documents.
64 provider \- OpenSSL operation implementation providers
74 A \fIprovider\fR, in OpenSSL terms, is a unit of code that provides one
91 functions in the form of an \fBOSSL_DISPATCH\fR\|(3) array, and by extension,
[all …]
|
| H A D | ossl-guide-libraries-introduction.7 | 1 .\" -*- mode: troff; coding: utf-8 -*-
19 .\" \*(C` and \*(C' are quotes in nroff, nothing in troff, for use with C<>.
29 .\" Escape single quotes in literal strings from groff's Unicode transform.
35 .\" entries marked with X<> in POD. Of course, you'll have to process the
36 .\" output yourself in some meaningful fashion.
57 .IX Title "OSSL-GUIDE-LIBRARIES-INTRODUCTION 7ossl"
58 .TH OSSL-GUIDE-LIBRARIES-INTRODUCTION 7ossl 2025-09-30 3.5.4 OpenSSL
60 .\" way too many mistakes in technical documents.
64 ossl\-guide\-libraries\-introduction
65 \&\- OpenSSL Guide: An introduction to the OpenSSL libraries
[all …]
|
| H A D | provider-cipher.7 | 1 .\" -*- mode: troff; coding: utf-8 -*-
19 .\" \*(C` and \*(C' are quotes in nroff, nothing in troff, for use with C<>.
29 .\" Escape single quotes in literal strings from groff's Unicode transform.
35 .\" entries marked with X<> in POD. Of course, you'll have to process the
36 .\" output yourself in some meaningful fashion.
57 .IX Title "PROVIDER-CIPHER 7ossl"
58 .TH PROVIDER-CIPHER 7ossl 2025-09-30 3.5.4 OpenSSL
60 .\" way too many mistakes in technical documents.
64 provider\-cipher \- The cipher library <\-> provider functions
72 \& * None of these are actual functions, but are displayed like this for
[all …]
|
| H A D | provider-kem.7 | 1 .\" -*- mode: troff; coding: utf-8 -*-
19 .\" \*(C` and \*(C' are quotes in nroff, nothing in troff, for use with C<>.
29 .\" Escape single quotes in literal strings from groff's Unicode transform.
35 .\" entries marked with X<> in POD. Of course, you'll have to process the
36 .\" output yourself in some meaningful fashion.
57 .IX Title "PROVIDER-KEM 7ossl"
58 .TH PROVIDER-KEM 7ossl 2025-09-30 3.5.4 OpenSSL
60 .\" way too many mistakes in technical documents.
64 provider\-kem \- The kem library <\-> provider functions
72 \& * None of these are actual functions, but are displayed like this for
[all …]
|
| /freebsd/contrib/mandoc/ |
| H A D | mandoc_headers.3 | 3 .\" Copyright (c) 2014-2022 Ingo Schwarze <schwarze@openbsd.org>
7 .\" copyright notice and this permission notice appear in all copies.
11 .\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR
13 .\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
15 .\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
28 included in the order shown in this manual page,
31 The headers and functions form three major groups:
42 .Bl -dash -offset indent -compact
75 .Bl -tag -width Ds
77 Memory allocation utility functions; can be used everywhere.
[all …]
|
| /freebsd/lib/libc/gen/ |
| H A D | getgrent.3 | 4 .\" Redistribution and use in source and binary forms, with or without
9 .\" 2. Redistributions in binary form must reproduce the above copyright
10 .\" notice, this list of conditions and the following disclaimer in the
19 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
23 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
24 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
65 These functions operate on the group database file
72 found in the include
75 .Bd -literal -offset indent
84 The functions
[all …]
|
| H A D | exec.3 | 4 .\" Redistribution and use in source and binary forms, with or without
9 .\" 2. Redistributions in binary form must reproduce the above copyright
10 .\" notice, this list of conditions and the following disclaimer in the
19 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
23 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
24 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
65 family of functions replaces the current process image with a
67 The functions described in this manual page are front-ends for the function
73 The initial argument for these functions is the pathname of a file which
78 and subsequent ellipses in the
[all …]
|
| H A D | getpwent.3 | 4 .\" Redistribution and use in source and binary forms, with or without
9 .\" 2. Redistributions in binary form must reproduce the above copyright
10 .\" notice, this list of conditions and the following disclaimer in the
19 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
23 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
24 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
65 These functions
70 Each entry in the database is defined by the structure
72 found in the include
75 .Bd -literal -offset indent
[all …]
|
| /freebsd/share/man/man9/ |
| H A D | bus_space.9 | 5 .\" Redistribution and use in source and binary forms, with or without
10 .\" 2. Redistributions in binary form must reproduce the above copyright
11 .\" notice, this list of conditions and the following disclaimer in the
16 .\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS
20 .\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
22 .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
32 .\" Redistribution and use in source and binary forms, with or without
37 .\" 2. Redistributions in binary form must reproduce the above copyright
38 .\" notice, this list of conditions and the following disclaimer in the
44 .\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS
[all …]
|
| H A D | hash.9 | 4 .\" Redistribution and use in source and binary forms, with or without
9 .\" 2. Redistributions in binary form must reproduce the above copyright
10 .\" notice, this list of conditions and the following disclaimer in the
18 .\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
22 .\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
23 .\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
43 .Nd general kernel hashing functions
67 functions are used to give a consistent and general interface to
69 These functions can be used to hash
76 argument is the length of the buffer in bytes.
[all …]
|
| H A D | iflibdd.9 | 6 .Nd Device Dependent Configuration Functions
9 .Ss "Soft Queue Setup and Teardown Functions"
10 .Ss "Mandatory Functions"
31 .Ss "Optional Functions"
42 .Ss "Device Setup and Teardown Functions"
43 .Ss "Mandatory Functions"
56 .Ss "Optional Functions"
75 .Ss "Device Configuration Functions"
76 .Ss "Mandatory Functions"
117 .Ss "Optional Functions"
[all …]
|
| /freebsd/lib/libc/softfloat/ |
| H A D | softfloat.txt | 9 -------------------------------------------------------------------------------
12 SoftFloat is a software implementation of floating-point that conforms to
13 the IEC/IEEE Standard for Binary Floating-Point Arithmetic. As many as four
20 IEC/IEEE Floating-Point Standard. Details about the standard are available
24 -------------------------------------------------------------------------------
27 SoftFloat is written in C and is designed to work with other C code. The
28 SoftFloat header files assume an ISO/ANSI-style C compiler. No attempt
29 has been made to accommodate compilers that are not ISO-conformant. In
33 Support for the extended double-precision and quadruple-precision formats
34 depends on a C compiler that implements 64-bit integer arithmetic. If the
[all …]
|
| /freebsd/crypto/openssl/doc/man7/ |
| H A D | ossl-guide-migration.pod | 5 ossl-guide-migration, migration_guide
6 - OpenSSL Guide: Migrating from older OpenSSL versions
17 For an overview of some of the key concepts introduced in OpenSSL 3.0 see
24 The FIPS provider in OpenSSL 3.1 includes some non-FIPS validated algorithms,
26 want to operate in a FIPS approved manner. The algorithms are:
47 uses an older version of OpenSSL will at the very least need to be recompiled in
51 changes may be required in some cases. Changes may also be required if
52 applications need to take advantage of some of the new features available in
57 In previous versions, OpenSSL was licensed under the L<dual OpenSSL and SSLeay
58 licenses|https://www.openssl.org/source/license-openssl-ssleay.txt>
[all …]
|
| H A D | provider.pod | 5 provider - OpenSSL operation implementation providers
19 A I<provider>, in OpenSSL terms, is a unit of code that provides one
37 functions in the form of an L<OSSL_DISPATCH(3)> array, and by extension,
38 a set of L<OSSL_ALGORITHM(3)>s (see L<openssl-core.h(7)>).
39 It may be a dynamically loadable module, or may be built-in, in
40 OpenSSL libraries or in the application.
43 If it's built-in, the initialization function may have any name.
48 const OSSL_DISPATCH *in, const OSSL_DISPATCH **out,
54 For the provider itself, it is passed to some of the functions given in the
55 dispatch array I<in>.
[all …]
|
| H A D | ossl-guide-libraries-introduction.pod | 5 ossl-guide-libraries-introduction
6 - OpenSSL Guide: An introduction to the OpenSSL libraries
14 encryption, digital signatures, hash functions, etc. It additionally supplies
19 example the "BIO" functions provide capabilities for abstracting I/O, e.g. via a
22 The C<libssl> library provides functions to perform secure communication between
28 C<libcrypto>, and most applications that do this will directly use API functions
38 A provider in OpenSSL is a component that collects together algorithm
40 algorithm AES). In order to use an algorithm you must have at least one
44 Providers may either be "built-in" or in the form of a separate loadable module
45 file (typically one ending in ".so" or ".dll" dependent on the platform). A
[all …]
|
| /freebsd/sys/contrib/device-tree/Bindings/pinctrl/ |
| H A D | marvell,armada-37xx-pinctrl.txt | 12 ------------------------
16 Refer to pinctrl-bindings.txt in this directory for details of the
22 - compatible: "marvell,armada3710-sb-pinctrl", "syscon, "simple-mfd"
24 "marvell,armada3710-nb-pinctrl", "syscon, "simple-mfd"
26 - reg: The first set of register are for pinctrl/gpio and the second
28 - interrupts: list of the interrupt use by the gpio
30 Available groups and functions for the North bridge:
33 - pins 20-24
34 - functions jtag, gpio
37 - pins 8-10
[all …]
|
| /freebsd/crypto/openssl/doc/designs/ |
| H A D | slh-dsa.md | 1 SLH-DSA Design
4 This document covers OpenSSL specific SLH-DSA implementation details.
5 FIPS 205 clearly states most of the requirements of SLH-DSA and has comprehensive
8 SLH_DSA Parameters & Functions
9 ------------------------------
11 There are 12 different parameter sets in FIPS 205. (See Section 11)
12 There are constants related to these, as well as there being a group of functions
17 OpenSSL will have 12 different key managers and 12 corresponding signature functions.
18 The names used are of the form "SLH-DSA-SHA2-128s" and "SLH-DSA-SHAKE-128f".
20 There are 7 hash functions used. The algorithms using SHAKE have a much simpler
[all …]
|
| /freebsd/secure/lib/libcrypto/man/man3/ |
| H A D | PEM_read_bio_PrivateKey.3 | 1 .\" -*- mode: troff; coding: utf-8 -*-
19 .\" \*(C` and \*(C' are quotes in nroff, nothing in troff, for use with C<>.
29 .\" Escape single quotes in literal strings from groff's Unicode transform.
35 .\" entries marked with X<> in POD. Of course, you'll have to process the
36 .\" output yourself in some meaningful fashion.
58 .TH PEM_READ_BIO_PRIVATEKEY 3ossl 2025-09-30 3.5.4 OpenSSL
60 .\" way too many mistakes in technical documents.
95 PEM_write_bio_PKCS7, PEM_write_PKCS7 \- PEM routines
206 The following functions have been deprecated since OpenSSL 3.0, and can be
265 All of the functions described on this page that have a \fITYPE\fR of \fBDH\fR, \fBDSA\fR
[all …]
|
| /freebsd/crypto/heimdal/lib/hx509/ |
| H A D | doxygen.c | 6 * Redistribution and use in source and binary forms, with or without
13 * 2. Redistributions in binary form must reproduce the above copyright
14 * notice, this list of conditions and the following disclaimer in the
24 * ARE DISCLAIMED. IN NO EVENT SHALL THE INSTITUTE OR CONTRIBUTORS BE LIABLE
28 * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
29 * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
44 * Sections in this manual are:
45 * - @ref page_name
46 * - @ref page_cert
47 * - @ref page_keyset
[all …]
|
| /freebsd/lib/libc/locale/ |
| H A D | DESIGN.xlocale | 8 - Manipulation of per-thread locales (POSIX)
9 - Locale-aware functions taking an explicit locale argument (Darwin)
14 -----
22 With this in mind, various libc-private functions have been modified to take a
25 variants of these functions, to make it harder for accidental uses of the
26 global-locale versions to slip in.
29 --------------
31 A locale is encapsulated in a `locale_t`, which is an opaque type: a pointer to
37 A locale_t is almost immutable after creation. There are no functions that modify it,
47 with each locale. These are used by various functions that previously had a
[all …]
|
| H A D | xlocale.3 | 6 .\" Redistribution and use in source and binary forms, with or without
11 .\" 2. Redistributions in binary form must reproduce the above copyright
12 .\" notice, this list of conditions and the following disclaimer in the
18 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
22 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
23 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
32 .Nd Thread-safe extended locale support
36 .In xlocale.h
38 The extended locale support includes a set of functions for setting
39 thread-loca
[all...] |
| /freebsd/lib/msun/man/ |
| H A D | math.3 | 4 .\" Redistribution and use in source and binary forms, with or without
9 .\" 2. Redistributions in binary form must reproduce the above copyright
10 .\" notice, this list of conditions and the following disclaimer in the
19 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
23 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
24 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
33 .Nd "floating-point mathematical library"
40 .Bl -column "<complex.h>" "polymorphic (type-generic) versions of functions" -compact -offset indent
46 The rest of this manual page describes the functions provided by
54 .Sh "LIST OF FUNCTIONS"
[all …]
|