| /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 …]
|
| H A D | gssapi.3 | 1 .\" -*- nroff -*-
34 GSS-API Library (libgssapi, -lgssapi)
38 The Generic Security Service Application Programming Interface
42 Typically, GSS-API callers will be application protocols into which
44 provided by the GSS-API.
45 The GSS-API allows a caller application to authenticate a principal
46 identity associated with a peer application, to delegate rights to a
49 on a per-message basis.
51 There are four stages to using the GSS-API:
52 .Bl -tag -width "a)"
[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/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
40 --------------------------
48 ---------------------
51 form of "control commands". These allow an application to expose to the
53 implementation supports, and for an application to directly feed string
54 based input to those ENGINEs, in the form of name-value pairs. This is an
[all …]
|
| /freebsd/secure/lib/libcrypto/man/man3/ |
| H A D | CRYPTO_get_ex_new_index.3 | 18 .\" Set up some character translations and predefined strings. \*(-- will
24 .tr \(*W-
27 . ds -- \(*W-
29 . if (\n(.H=4u)&(1m=24u) .ds -- \(*W\h'-12u'\(*W\h'-12u'-\" diablo 10 pitch
30 . if (\n(.H=4u)&(1m=20u) .ds -- \(*W\h'-12u'\(*W\h'-8u'-\" diablo 12 pitch
37 . ds -- \|\(em\|
71 .\" Fear. Run. Save yourself. No user-serviceable parts.
81 . ds #H ((1u-(\\\\n(.fu%2u))*.13m)
97 . ds ' \\k:\h'-(\\n(.wu*8/10-\*(#H)'\'\h"|\\n:u"
98 . ds ` \\k:\h'-(\\n(.wu*8/10-\*(#H)'\`\h'|\\n:u'
[all …]
|
| H A D | SSL_export_keying_material.3 | 18 .\" Set up some character translations and predefined strings. \*(-- will
24 .tr \(*W-
27 . ds -- \(*W-
29 . if (\n(.H=4u)&(1m=24u) .ds -- \(*W\h'-12u'\(*W\h'-12u'-\" diablo 10 pitch
30 . if (\n(.H=4u)&(1m=20u) .ds -- \(*W\h'-12u'\(*W\h'-8u'-\" diablo 12 pitch
37 . ds -- \|\(em\|
71 .\" Fear. Run. Save yourself. No user-serviceable parts.
81 . ds #H ((1u-(\\\\n(.fu%2u))*.13m)
97 . ds ' \\k:\h'-(\\n(.wu*8/10-\*(#H)'\'\h"|\\n:u"
98 . ds ` \\k:\h'-(\\n(.wu*8/10-\*(#H)'\`\h'|\\n:u'
[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 …]
|
| H A D | default_colors.3x | 2 .\" Copyright 2018-2023,2024 Thomas E. Dickey *
3 .\" Copyright 2000-2011,2016 Free Software Foundation, Inc. *
33 .TH default_colors 3X 2024-04-13 "ncurses @NCURSES_MAJOR@.@NCURSES_MINOR@" "Library calls"
46 \fB\%assume_default_colors\fP \-
59 These terminals allow the application to reset color to an unspecified
72 Full-screen applications that use default colors can achieve similar
77 foreground/background colors to color number \-1.
78 So init_pair(x,COLOR_RED,\-1)
80 and init_pair(x,\-1,COLOR_BLUE) will
85 This function recognizes a special color number \-1,
[all …]
|
| H A D | form_driver.3x | 3 .\" Copyright 2018-2023,2024 Thomas E. Dickey *
4 .\" Copyright 1998-2016,2017 Free Software Foundation, Inc. *
32 .TH form_driver 3X 2024-04-20 "ncurses @NCURSES_MAJOR@.@NCURSES_MINOR@" "Library calls"
39 \fBform_driver_w\fP \-
40 command-processing loop of the form system
55 which are distinct from the key- and character codes returned
86 REQ_DEL_WORD Delete blank-delimited word at cursor.
146 The form driver provides low-level control over updates to the form fields.
149 meet whatever constraints an application may attach using \fBset_field_type\fP.
171 mouse event is translated into one of the above pre-defined requests.
[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...] |
| H A D | snps,dw-pcie-ep.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/pci/snps,dw-pcie-ep.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Jingo
[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...] |
| H A D | sctp_getaddrlen.3 | 14 .\" without specific prior written permission.
45 function returns the size of a specific address family.
47 is provided for application binary compatibility since it
48 provides the application with the size the operating system
49 thinks the specific address family is.
68 system expects for the specific address family or -1.
73 .Bl -tag -width Er
|
| /freebsd/crypto/openssl/crypto/engine/ |
| H A D | README.md | 1 Notes on engines of 2001-09-24
9 lynched for sticking all this in CHANGES.md or the commit mails :-).
37 selection, eg. in SSL/TLS, or by user-controllable configuration.
49 into ENGINE is storage - the OBJ_NAME-based storage used by EVP to register
50 ciphers simultaneously registers cipher *types* and cipher *implementations* -
53 solution is necessarily that ENGINE-provided ciphers simply are not registered,
56 for cleanup, modularity, and DSO support - yet EVP_CIPHERs, as exposed to
64 linker hassles if nothing else - linking a 1-line application that calls 2 basic
76 work prior to ENGINE :-). Ie. RSA now has a "RSA_METHOD" pointer again - this
82 for a fallback ENGINE that encapsulates default implementations - we can simply
[all …]
|
| /freebsd/crypto/heimdal/lib/wind/ |
| H A D | rfc3490.txt | 37 repertoire (Unicode), but IDNA allows the non-ASCII characters to be
38 represented using only the ASCII characters already allowed in so-
39 called host names today. This backward-compatible representation is
49 1.3 Brief overview for application developers................. 4
63 3.2.2. Non-domain-name data types stored in domain names... 9
87 (beginning with a special prefix) to represent non-ASCII name labels.
88 Lower-layer protocols need not be aware of this; therefore IDNA does
97 application wants to use non-ASCII characters in domain names, IDNA
98 is the only currently-defined option. Adding IDNA support to an
99 existing application entails changes to the application only, and
[all …]
|
| /freebsd/contrib/elftoolchain/libdwarf/ |
| H A D | dwarf_object_init.3 | 25 .\" $Id: dwarf_object_init.3 3644 2018-10-15 19:55:01Z jkoshy $
32 .Nd allocate a DWARF debug descriptor with application-specific file \
51 instance that uses application-supplied access methods to read file
96 .Bl -tag -width indent
99 with a pointer to application-private state.
100 .Bd -literal -offset indent
107 .Bl -tag -width ".Ar methods" -compact
109 This field points to application-specific state that will be passed as
116 This structure specifies the functions implementing low-level access.
117 .Bd -literal -offset indent
[all …]
|
| /freebsd/share/man/man3/ |
| H A D | pthread_key_delete.3 | 15 .\" 4. Neither the name of the author nor the names of any co-contributors
17 .\" without specific prior written permission.
36 .Nd delete a thread-specific data key
46 function deletes a thread-specific data key previously returned by
48 The thread-specific data values associated with
53 It is the responsibility of the application to free any
54 application storage or perform any cleanup actions for data structures
55 related to the deleted key or associated thread-specific data in any threads;
84 .Bl -tag -width Er
98 .St -p1003.1-96 .
|