| /freebsd/secure/lib/libcrypto/man/man7/ |
| H A D | openssl-quic.7 | 1 .\" -*- mode: troff; coding: utf-8 -*-
57 .IX Title "OPENSSL-QUIC 7ossl"
58 .TH OPENSSL-QUIC 7ossl 2025-09-30 3.5.4 OpenSSL
64 openssl\-quic \- OpenSSL QUIC
82 Default stream mode versus multi-stream mode for clients;
84 The changes to existing libssl APIs which are driven by QUIC-related
92 New, QUIC-specific APIs.
96 stream mode, which is intended to provide compatibility with existing non-QUIC
97 application usage patterns. In this mode, the connection has a single stream
100 client-initiated or server-initiated from a QUIC perspective depends on whether
[all …]
|
| /freebsd/crypto/openssl/doc/man7/ |
| H A D | openssl-quic.pod | 5 openssl-quic - OpenSSL QUIC
28 Default stream mode versus multi-stream mode for clients;
32 The changes to existing libssl APIs which are driven by QUIC-related
46 New, QUIC-specific APIs.
53 stream mode, which is intended to provide compatibility with existing non-QUIC
54 application usage patterns. In this mode, the connection has a single stream
57 client-initiated or server-initiated from a QUIC perspective depends on whether
62 instead adopt the multi-stream API. See the RECOMMENDATIONS FOR NEW APPLICATIONS
68 multi-stream mode. By default, a newly created QUIC connection SSL object uses
80 whether a stream is client-initiated or server-initiated. In default stream
[all …]
|
| /freebsd/lib/libgssapi/ |
| H A D | gss_init_sec_context.3 | 1 .\" -*- nroff -*-
33 .Nd Initiate a security context with a peer application
56 application and a remote peer.
61 the peer application, where the peer application will present it to
68 application; if so,
76 application, passing the reply token to
85 .Bd -literal
89 input_token->length = 0;
109 if (output_token->length != 0) {
133 .Bl -bullet
[all …]
|
| H A D | gss_acquire_cred.3 | 1 .\" -*- nroff -*-
33 .Nd Obtain a GSS-API credential handle for pre-existing credentials
50 Allows an application to acquire a handle for a pre-existing
52 GSS-API implementations must impose a local
53 access-control policy on callers of this routine to prevent
61 implementation-specific extensions to the API.
94 since implementations are likely to provide mechanism-specific ways
95 of obtaining GSS-API initiator credentials from the system login
111 If credential acquisition is time-consuming for a mechanism,
118 Such mechanism-specific implementation
[all …]
|
| H A D | gss_accept_sec_context.3 | 1 .\" -*- nroff -*-
33 .Nd Accept a security context initiated by a peer application
53 Allows a remotely initiated security context between the application and a remote
57 which should be transferred to the peer application,
58 where the peer application will present it to
67 required from the peer application; if so,
72 application, passing the token to
84 .Bd -literal
103 if (output_token->length != 0) {
128 .Dv GSS_C_PROT_READY_FLAG , indicating that per-message services may be
[all …]
|
| H A D | gss_inquire_context.3 | 1 .\" -*- nroff -*-
56 .Bl -tag -width ".It locally_initiated"
58 Mechanism specific status code.
64 and if the application invoking
68 Storage associated with this name must be freed by the application
76 Storage associated with this name must be freed by the application
102 treated as read-only by the application;
103 in particular the application should not attempt to free it.
113 a specific service option.
118 logically-ANDed with the
[all …]
|
| H A D | gss_add_cred.3 | 1 .\" -*- nroff -*-
53 Adds a credential-element to a credential.
54 The credential-element is identified by the name of the principal to
56 GSS-API implementations must impose a local access-control policy on
58 credential-elements to which they are not entitled.
62 mechanism-specific authentication data,
63 rather than merely acquiring a GSS-API handle to existing data.
66 should be defined in implementation-specific extensions to the API.
89 since implementations are likely to provide mechanism-specific ways of
90 obtaining GSS-API initiator credentials from the system login process.
[all …]
|
| /freebsd/secure/lib/libcrypto/man/man3/ |
| H A D | SSL_shutdown.3 | 1 .\" -*- mode: troff; coding: utf-8 -*-
58 .TH SSL_SHUTDOWN 3ossl 2025-09-30 3.5.4 OpenSSL
64 SSL_shutdown, SSL_shutdown_ex \- shut down a TLS/SSL or QUIC connection
85 \&\fBSSL_shutdown_ex()\fR is an extended version of \fBSSL_shutdown()\fR. If non-NULL, \fIargs\fR
88 zero-initialized. If \fIargs\fR is NULL, the behaviour is the same as passing a
89 zero-initialised \fBSSL_SHUTDOWN_EX_ARGS\fR structure. Currently, all extended
107 .SH "TLS AND DTLS-SPECIFIC CONSIDERATIONS"
108 .IX Header "TLS AND DTLS-SPECIFIC CONSIDERATIONS"
118 shutdown process was first initiated by the local application or by the peer.
119 .SS "Locally-Initiated Shutdown"
[all …]
|
| H A D | CRYPTO_get_ex_new_index.3 | 1 .\" -*- mode: troff; coding: utf-8 -*-
58 .TH CRYPTO_GET_EX_NEW_INDEX 3ossl 2025-09-30 3.5.4 OpenSSL
68 \&\- functions supporting application\-specific data
102 Several OpenSSL structures can have application-specific data attached to them,
104 The specific structures are:
124 In addition, the \fBAPP\fR name is reserved for use by application code.
130 The API described here is used by OpenSSL to manipulate exdata for specific
131 structures. Since the application data can be anything at all it is passed
153 This will replace the callbacks with no-ops
156 To set or get the exdata on an object, the appropriate type-specific
[all …]
|
| H A D | SSL_export_keying_material.3 | 1 .\" -*- mode: troff; coding: utf-8 -*-
58 .TH SSL_EXPORT_KEYING_MATERIAL 3ossl 2025-09-30 3.5.4 OpenSSL
66 \&\- obtain keying material for application use
87 application to use some of this keying material for its own purposes in
96 available when the client attempts to send 0\-RTT data. For the server, it is
97 only available when the server accepts 0\-RTT data.
99 An application may need to securely establish the context within which this
101 application session, application algorithms or parameters, or the lifetime of
102 the context. The context value is left to the application but must be the same
106 \&\fBout\fR. The application specific context should be supplied in the location
[all …]
|
| H A D | ENGINE_add.3 | 1 .\" -*- mode: troff; coding: utf-8 -*-
58 .TH ENGINE_ADD 3ossl 2025-09-30 3.5.4 OpenSSL
102 \&\- ENGINE cryptographic module support
238 reference-counted mechanism to allow them to be dynamically loaded in and
239 out of the running application.
245 \& RSA_METHOD \- for providing alternative RSA implementations
247 \& \- similarly for other OpenSSL APIs
248 \& EVP_CIPHER \- potentially multiple cipher algorithms (indexed by \*(Aqnid\*(Aq)
249 \& EVP_DIGEST \- potentially multiple hash algorithms (indexed by \*(Aqnid\*(Aq)
250 \& key\-loading \- loading public and/or private EVP_PKEY keys
[all …]
|
| /freebsd/crypto/openssl/doc/man3/ |
| H A D | SSL_export_keying_material.pod | 7 - obtain keying material for application use
28 application to use some of this keying material for its own purposes in
37 available when the client attempts to send 0-RTT data. For the server, it is
38 only available when the server accepts 0-RTT data.
40 An application may need to securely establish the context within which this
42 application session, application algorithms or parameters, or the lifetime of
43 the context. The context value is left to the application but must be the same
47 B<out>. The application specific context should be supplied in the location
57 An application specific label should be provided in the location pointed to by
60 (L<https://www.iana.org/assignments/tls-parameters/tls-parameters.xhtml#exporter-labels>).
[all …]
|
| H A D | CRYPTO_get_ex_new_index.pod | 9 - functions supporting application-specific data
43 Several OpenSSL structures can have application-specific data attached to them,
45 The specific structures are:
63 In addition, the B<APP> name is reserved for use by application code.
69 The API described here is used by OpenSSL to manipulate exdata for specific
70 structures. Since the application data can be anything at all it is passed
92 This will replace the callbacks with no-ops
95 To set or get the exdata on an object, the appropriate type-specific
98 B<idx> parameter should be an already-created index value.
101 and returned on a subsequent "get" call. If the application is going to
[all …]
|
| /freebsd/contrib/ofed/libmlx5/ |
| H A D | mlx5dv.7 | 1 .\" -*- nroff -*-
2 .\" Licensed under the OpenIB.org (MIT) - See COPYING.md
4 .TH MLX5DV 7 2017-02-02 1.0.0
6 mlx5dv \- Direct verbs for mlx5 devices
13 provider specific implementation. While this abstraction has the advantage
18 It exposes mlx5 specific low level data path (send/receive/completion)
19 operations, allowing the application to bypass the libibverbs data path API.
21 This interface consists from one hardware specific header file
23 to mlx5 specific structures.
28 Once an application uses the direct flow the locking scheme is fully managed
[all …]
|
| /freebsd/crypto/krb5/src/windows/ |
| H A D | version.rc | 22 #define RELTAIL "-" KRB5_RELTAIL
44 #define K5_COPYRIGHT "Copyright (C) 1997-2025 by the Massachusetts Institute of Technology\0"
53 * BEGIN SPECIFIC VERSION INFO for GSS and Kerberos version resources
57 #define K5_DESCRIPTION "Kerberos v5 support - internal support code for " KRB5_PRODUCTNAME_STR
68 #define K5_DESCRIPTION "COM_ERR - Common Error Handler for " KRB5_PRODUCTNAME_STR "\0"
79 #define K5_DESCRIPTION "PROFILE - Profile Library " KRB5_PRODUCTNAME_STR "\0"
90 #define K5_DESCRIPTION "Kerberos v5 - " KRB5_PRODUCTNAME_STR "\0"
101 #define K5_DESCRIPTION "GSSAPI - GSS API implementation for Kerberos 5 mechanism\0"
130 #define K5_DESCRIPTION "MIT Kerberos Ticket Manager - " KRB5_PRODUCTNAME_STR "\0"
137 #define K5_DESCRIPTION "Leash Helper API - " KRB5_PRODUCTNAME_STR "\0"
[all …]
|
| /freebsd/crypto/openssl/ |
| H A D | README-ENGINES.md | 5 ----------------
12 by the [PROVIDER API](README-PROVIDERS.md), it is deprecated in OpenSSL
19 Built-in ENGINE implementations
20 -------------------------------
22 There are currently built-in ENGINE implementations for the following
25 - Microsoft CryptoAPI
26 - VIA Padlock
27 - nCipher CHIL
40 --------------------------
48 ---------------------
[all …]
|
| /freebsd/contrib/jemalloc/ |
| H A D | TUNING.md | 7 a specific application / workload, it is common to improve system level metrics
8 by a few percent, or make favorable trade-offs.
19 application threads, since unused memory purging is shifted to the dedicated
21 application inactivity is avoided with background threads.
42 operating system, and therefore provides a fairly straightforward trade-off
47 Suggested: tune the values based on the desired trade-offs.
71 * High resource consumption application, prioritizing CPU utilization:
77 * High resource consumption application, prioritizing memory usage:
84 * Low resource consumption application:
90 * Extremely conservative -- minimize memory usage at all costs, only suitable when
[all …]
|
| /freebsd/crypto/krb5/src/plugins/kdb/db2/libdb2/man/ |
| H A D | db_txn.3 | 20 .\" without specific prior written permission.
39 db_txn \- transaction management functions
75 specific details of the transaction support.
93 access methods) is that write-ahead logging is provided by
95 to record both before- and after-image logging.
96 Locking follows a two-phase protocol and is implemented by
128 Use two-phase locking.
134 Provide redo-only logging (not currently implemented).
137 Provide undo-only logging (not currently implemented).
140 Provide undo/redo write-ahead logging.
[all …]
|
| /freebsd/contrib/file/magic/Magdir/ |
| H A D | marc21 | 1 #--------------------------------------------
7 # of bibliographic and related information in machine-readable
11 # leader position 20-21 must be 45
12 # and 22-23 also 00 so far, but we check that later.
16 # leader starts with 5 digits, followed by codes specific to MARC format
17 >>0 regex/1l (^[0-9]{5})[acdnp][^bhlnqsu-z] MARC21 Bibliographic
18 !:mime application/marc
19 >>0 regex/1l (^[0-9]{5})[acdnosx][z] MARC21 Authority
20 !:mime application/marc
21 >>0 regex/1l (^[0-9]{5})[cdn][uvxy] MARC21 Holdings
[all …]
|
| /freebsd/contrib/ncurses/man/ |
| H A D | menu_driver.3x | 2 .\" Copyright 2018-2023,2024 Thomas E. Dickey *
3 .\" Copyright 1998-2010,2017 Free Software Foundation, Inc. *
31 .TH menu_driver 3X 2024-03-16 "ncurses @NCURSES_MAJOR@.@NCURSES_MINOR@" "Library calls"
37 \fBmenu_driver\fP \-
38 command-processing loop of the menu system
51 which are distinct from the key- and character codes
119 If the second argument is one of the above pre-defined requests, the
123 mouse event is translated into one of the above pre-defined requests.
131 a REQ_SCR_UPAGE is generated for a double-click and
133 a REQ_FIRST_ITEM is generated for a triple-click.
[all …]
|
| /freebsd/crypto/openssl/doc/designs/quic-design/ |
| H A D | quic-requirements.md | 9 -------------------------
14 [posted](https://mta.openssl.org/pipermail/openssl-project/2021-October/002764.html)
15 and that were specific to QUIC
18 fully functional QUIC implementation over a series of releases (2-3).
28 * The application must have the ability to be in control of the event loop without
29 requiring callbacks to process the various events. An application must also have
42 non-goal of the initial release). Our expectation is that other libraries will
52 part of this activity - we can change major release numbers even if APIs remain
56 is a non-goal.
63 1. [Cloudfare](https://cloudflare-quic.com/)
[all …]
|
| /freebsd/sys/contrib/device-tree/Bindings/pci/ |
| H A D | snps,dw-pcie-common.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/pci/snps,dw-pci
[all...] |
| /freebsd/crypto/openssl/doc/designs/ |
| H A D | ossl-provider-load-ex.md | 1 OSSL_PROVIDER_load_ex - activating providers with run-time configuration
4 Currently any provider run-time activation requires the presence of the
7 work for a particular application. For real-world systems it may require
11 We need a possibility to initialize providers on per-application level
12 according to per-application parameters. It's necessary for example for PKCS#11
34 Real-world cases
35 ----------------
37 Many applications use PKCS#11 API with specific drivers. OpenSSL PKCS#11
38 provider <https://github.com/latchset/pkcs11-provider> also provides a set of
43 2. Load/activate a provider run-time with parameters
[all …]
|
| /freebsd/contrib/elftoolchain/libelf/ |
| H A D | elf.3 | 1 .\" Copyright (c) 2006-2008,2011,2019 Joseph Koshy. All rights reserved.
24 .\" $Id: elf.3 3743 2019-06-12 19:36:30Z jkoshy $
39 provides functions that allow an application to read and manipulate
44 and word-size independent way, allowing an application to read and
45 create ELF objects for 32 and 64 bit architectures and for little-
46 and big-endian machines.
59 specific way.
85 for little-endian architectures and
87 for big-endian architectures.
101 An application would work with ELF data in its
[all …]
|
| /freebsd/lib/libc/net/ |
| H A D | sctp_recvmsg.3 | 14 .\" without specific prior written permission.
58 They are used by one-to-one (SOCK_STREAM) type sockets after a successful
60 call or after the application has performed a
64 For a one-to-many (SOCK_SEQPACKET) type socket, an endpoint may call
74 Or, an application may also receive a message after having
115 indicated by a return value of -1 with
139 socket has been placed in non-blocking I/O mode.
148 .Bd -litera
[all...] |