| /freebsd/contrib/file/magic/Magdir/ |
| H A D | python | 14 !:mime application/x-bytecode.python
16 !:mime application/x-bytecode.python
18 !:mime application/x-bytecode.python
20 !:mime application/x-bytecode.python
22 !:mime application/x-bytecode.python
24 !:mime application/x-bytecode.python
26 !:mime application/x-bytecode.python
28 !:mime application/x-bytecode.python
30 !:mime application/x-bytecode.python
32 !:mime application/x-bytecode.python
[all …]
|
| H A D | epoc | 11 !:mime application/x-epoc-font
13 !:mime application/x-epoc-pdriver
15 !:mime application/x-epoc-clipboard
18 >4 lelong 0x1000006A application information file
24 !:mime application/x-epoc-voice
26 !:mime application/x-epoc-word
28 !:mime application/x-epoc-opl
30 !:mime application/x-epoc-data
33 !:mime application/x-epoc-sheet
35 !:mime application/x-epoc-eini
[all …]
|
| H A D | ole2compounddocs | 17 !:mime application/msword
105 #!:mime application/x-ole-storage
106 !:mime application/x-bentley-dgn
113 !:mime application/vnd.wordperfect
121 !:mime application/vnd.ms-works
128 !:mime application/vnd.ms-works
137 !:mime application/vnd.ms-excel
145 !:mime application/vnd.ms-powerpoint
153 #!:mime application/vnd.ms-outlook
154 !:mime application/x-ms-srs
[all …]
|
| H A D | wordprocessors | 24 !:mime application/vnd-ms-works
25 #!:mime application/x-msworks
35 #!:mime application/x-mspublisher
37 # https://web.archive.org/web/20200930085807/https://reposcope.com/mimetype/application/vnd.ms-publ…
38 !:mime application/vnd.ms-publisher
47 #!:mime application/octet-stream
48 !:mime application/x-cosmi
62 #!:mime application/octet-stream
63 !:mime application/x-wordperfect-wpm
68 #!:mime application/octet-stream
[all …]
|
| H A D | compress | 13 !:mime application/x-compress
30 # KPR KOffice/Calligra KPresenter application/x-kpresenter
31 # KPT KOffice/Calligra KPresenter template? application/x-kpresenter
44 #!:mime application/octet-stream
53 #!:mime application/octet-stream
62 !:mime application/gzip
68 #!:mime application/x-compressed-tar
69 #!:mime application/x-virtualbox-vbox-extpack
85 !:mime application/gzip
87 #!:mime application/x-compressed-tar
[all …]
|
| H A D | archive | 80 !:mime application/x-gtar
83 !:mime application/x-gtar
86 !:mime application/x-gtar
89 !:mime application/x-tar
95 !:mime application/x-tar
102 !:mime application/x-gtar
110 !:mime application/x-ustar
114 !:mime application/x-ustar
118 !:mime application/x-ustar
204 #!:mime application/x-gtar
[all …]
|
| H A D | frame | 18 #!:mime application/octet-stream
19 # https://www.iana.org/assignments/media-types/application/vnd.framemaker
20 !:mime application/vnd.framemaker
55 # https://www.iana.org/assignments/media-types/application/vnd.mif
56 !:mime application/vnd.mif
73 #!:mime application/x-mif
74 !:mime application/vnd.framemaker
89 #!:mime application/octet-stream
90 #!:mime application/x-mif
91 !:mime application/x-font-framemaker
[all …]
|
| /freebsd/contrib/ntp/libntp/lib/isc/include/isc/ |
| H A D | app.h | 28 * \brief ISC Application Support
33 * thread of the application:
39 * and then block until application
45 * application should shutdown itself.
57 * This module also supports per-thread 'application contexts'. With this
58 * mode, a thread-based application will have a separate context, in which
60 * not caught in this mode, so that the application can handle the signals
71 * application context must ensure that isc_app_ctxstart() with the
123 * This structure is actually just the common prefix of an application context
149 * \brief Start an ISC library application.
[all …]
|
| /freebsd/secure/lib/libcrypto/man/man7/ |
| H A D | openssl-quic.7 | 97 application usage patterns. In this mode, the connection has a single stream
123 mode, if a client application calls \fBSSL_read\fR\|(3) first before any call to
124 \&\fBSSL_write\fR\|(3) on the connection, it is assumed that the application protocol
128 application calls \fBSSL_write\fR\|(3) before any call to \fBSSL_read\fR\|(3) on the
151 SSL object fail. Instead, an application calls \fBSSL_new_stream\fR\|(3) or
153 receiving application data using \fBSSL_read\fR\|(3) and \fBSSL_write\fR\|(3).
186 An application may also choose to implement a custom BIO. The new
197 Traditionally, whether the application-level I/O APIs (such as \fBSSL_read\fR\|(3)
201 application-level blocking mode using \fBSSL_set_blocking_mode\fR\|(3). See
205 application can still enjoy blocking semantics for calls to application-level
[all …]
|
| H A D | ossl-guide-quic-introduction.7 | 86 allowing application protocols built on QUIC to create arbitrarily many
88 application protocol to avoid problems where one packet of data is held up
90 "head-of-line blocking"). It also enables an application to open additional
101 allowing a connection to be initiated to a server and application data to be
113 .IP "Implemented as application library" 4
114 .IX Item "Implemented as application library"
116 implemented as an application library rather than by an operating system, an
117 application can gain the benefit of QUIC without needing to wait for an OS
119 can be delivered as quickly as an application can be updated without dependency
129 performed on a regular basis regardless of whether application data is being
[all …]
|
| H A D | openssl-quic-concurrency.7 | 80 An explicit QUIC domain is created by and visible to the application as a QUIC
85 creation of a QUIC connection or listener SSL object; the application does not
90 application. Applications can use an implicit QUIC domain for ease of use and to
94 processing model is the same and the application must choose an appropriate
104 application-synchronised single-threaded usage.
109 multi-threaded usage and provides assistance to an application for handling QUIC
115 synchronisation. It is entirely up to the application to synchronise access to
118 This concurrency model is also useful for an application which wants to use the
131 which spend the majority of their time in application logic and not in QUIC I/O
140 timeout events are handled even if an application does not periodically call
[all …]
|
| /freebsd/secure/lib/libcrypto/man/man3/ |
| H A D | SSL_shutdown.3 | 118 shutdown process was first initiated by the local application or by the peer.
131 application's shutdown indication.
138 close_notify alert message, an application will be notified of this as an EOF
141 return \fBSSL_ERROR_ZERO_RETURN\fR), after all application data sent by the peer
142 prior to initiating the shutdown has been read. An application should handle
145 application data using \fBSSL_write\fR\|(3) before doing so. If an application does
164 An application can then detect completion of the shutdown process by calling
172 peer's close_notify alert is still provided to the application. It also ensures
178 it is called when the application has not read all pending application data
189 Alternatively, it is acceptable for an application to call \fBSSL_shutdown()\fR once
[all …]
|
| H A D | SSL_CTX_set_session_ticket_cb.3 | 68 SSL_CTX_decrypt_session_ticket_fn \- manage session ticket application data
89 \&\fBSSL_CTX_set_set_session_ticket_cb()\fR sets the application callbacks \fBgen_cb\fR
90 and \fBdec_cb\fR that are used by a server to set and get application data stored
94 \&\fBgen_cb\fR is the application defined callback invoked when a session ticket is
95 about to be created. The application can call \fBSSL_SESSION_set1_ticket_appdata()\fR
96 at this time to add application data to the session ticket. The value of \fBarg\fR
100 \&\fBdec_cb\fR is the application defined callback invoked after session ticket
101 decryption has been attempted and any session ticket application data is
109 \&\fBSSL_SESSION_set1_ticket_appdata()\fR sets the application data specified by
114 the application that a session ticket is about to be generated.
[all …]
|
| /freebsd/crypto/openssl/doc/designs/quic-design/ |
| H A D | quic-io-arch.md | 16 - The application must have the ability to be in control of the event loop
17 without requiring callbacks to process the various events. An application must
31 for application use of the libssl APIs.
34 for an application to do its own polling and make its own event
62 network. This is independent of and orthogonal to the application interface to
73 To function correctly and provide blocking semantics at the application level,
147 able to support blocking semantics at the application level. Applications
152 - Several threads are spawned which the application is not in control of.
153 This undermines our general approach of providing the application with control
154 over OpenSSL's use of resources, such as allowing the application to do its
[all …]
|
| /freebsd/crypto/openssl/doc/man3/ |
| H A D | SSL_shutdown.pod | 68 shutdown process was first initiated by the local application or by the peer.
82 application's shutdown indication.
90 close_notify alert message, an application will be notified of this as an EOF
93 return B<SSL_ERROR_ZERO_RETURN>), after all application data sent by the peer
94 prior to initiating the shutdown has been read. An application should handle
97 application data using L<SSL_write(3)> before doing so. If an application does
117 An application can then detect completion of the shutdown process by calling
125 peer's close_notify alert is still provided to the application. It also ensures
131 it is called when the application has not read all pending application data
143 Alternatively, it is acceptable for an application to call SSL_shutdown() once
[all …]
|
| H A D | SSL_CTX_set_session_ticket_cb.pod | 9 SSL_CTX_decrypt_session_ticket_fn - manage session ticket application data
30 SSL_CTX_set_set_session_ticket_cb() sets the application callbacks B<gen_cb>
31 and B<dec_cb> that are used by a server to set and get application data stored
35 B<gen_cb> is the application defined callback invoked when a session ticket is
36 about to be created. The application can call SSL_SESSION_set1_ticket_appdata()
37 at this time to add application data to the session ticket. The value of B<arg>
41 B<dec_cb> is the application defined callback invoked after session ticket
42 decryption has been attempted and any session ticket application data is
50 SSL_SESSION_set1_ticket_appdata() sets the application data specified by
55 the application that a session ticket is about to be generated.
[all …]
|
| /freebsd/crypto/openssl/doc/man7/ |
| H A D | ossl-guide-quic-introduction.pod | 32 allowing application protocols built on QUIC to create arbitrarily many
34 application protocol to avoid problems where one packet of data is held up
36 "head-of-line blocking"). It also enables an application to open additional
49 allowing a connection to be initiated to a server and application data to be
64 =item Implemented as application library
67 implemented as an application library rather than by an operating system, an
68 application can gain the benefit of QUIC without needing to wait for an OS
70 can be delivered as quickly as an application can be updated without dependency
84 performed on a regular basis regardless of whether application data is being
91 L<SSL_get_event_timeout(3)> which tells an application the amount of time that
[all …]
|
| H A D | openssl-quic.pod | 54 application usage patterns. In this mode, the connection has a single stream
81 mode, if a client application calls L<SSL_read(3)> first before any call to
82 L<SSL_write(3)> on the connection, it is assumed that the application protocol
86 application calls L<SSL_write(3)> before any call to L<SSL_read(3)> on the
110 SSL object fail. Instead, an application calls L<SSL_new_stream(3)> or
112 receiving application data using L<SSL_read(3)> and L<SSL_write(3)>.
159 An application may also choose to implement a custom BIO. The new
173 Traditionally, whether the application-level I/O APIs (such as L<SSL_read(3)>
177 application-level blocking mode using L<SSL_set_blocking_mode(3)>. See
183 application can still enjoy blocking semantics for calls to application-level
[all …]
|
| H A D | openssl-quic-concurrency.pod | 27 An explicit QUIC domain is created by and visible to the application as a QUIC
34 creation of a QUIC connection or listener SSL object; the application does not
41 application. Applications can use an implicit QUIC domain for ease of use and to
45 processing model is the same and the application must choose an appropriate
60 application-synchronised single-threaded usage.
69 multi-threaded usage and provides assistance to an application for handling QUIC
81 synchronisation. It is entirely up to the application to synchronise access to
84 This concurrency model is also useful for an application which wants to use the
99 which spend the majority of their time in application logic and not in QUIC I/O
110 timeout events are handled even if an application does not periodically call
[all …]
|
| /freebsd/lib/libgssapi/ |
| H A D | gssapi.3 | 38 The Generic Security Service Application Programming Interface
42 Typically, GSS-API callers will be application protocols into which
45 The GSS-API allows a caller application to authenticate a principal
46 identity associated with a peer application, to delegate rights to a
54 The application acquires a set of credentials with which it may prove
56 The application's credentials vouch for its global identity,
76 similar to those used by the initiating application,
85 the token to the peer application,
86 encapsulated if necessary in an application protocol.
87 On receipt of such a token, the peer application should pass it to a
[all …]
|
| /freebsd/crypto/openssl/doc/designs/quic-design/server/ |
| H A D | quic-polling.md | 9 …e Case A: Simple Blocking or Non-Blocking Application](#use-case-a--simple-blocking-or-non-blockin…
10 …+ [Use Case B: Application-Controlled Hierarchical Polling](#use-case-b--application-controlled-hi…
41 An application can create multiple QLSOs (see the [server API design
43 pair. Therefore an application needs to be able to poll:
57 - There are a large number of event types an application might want to poll on.
67 able for an application to request wakeup on the first of an arbitrary subset
76 - **Support external polling.** An application must be able to be in control
78 or poll(2)-style calls; the application handles all poll(2)-like calls to the
79 OS. The application must thereafter be able to find out from us what QUIC
147 ### Use Case A: Simple Blocking or Non-Blocking Application
[all …]
|
| /freebsd/crypto/krb5/src/lib/kadm5/ |
| H A D | kadm_err.et | 40 …ERSION, "API structure version specified by application is no longer supported (to fix, recompile …
41 …n specified by application is unknown to libraries (to fix, obtain current KADM5 API header files …
43 …API_VERSION, "API version specified by application is no longer supported by libraries (to fix, up…
44 …_API_VERSION, "API version specified by application is no longer supported by server (to fix, upda…
45 …n specified by application is unknown to libraries (to fix, obtain current KADM5 API header files …
46 error_code KADM5_NEW_SERVER_API_VERSION, "API version specified by application is unknown to server…
|
| /freebsd/contrib/ntp/sntp/libopts/ |
| H A D | COPYING.lgplv3 | 20 other than an Application or a Combined Work as defined below.
22 An "Application" is any work that makes use of an interface provided
28 Application with the Library. The particular version of the Library
35 based on the Application, and not on the Linked Version.
37 The "Corresponding Application Code" for a Combined Work means the
38 object code and/or source code for the Application, including any data
40 Application, but excluding the System Libraries of the Combined Work.
50 facility refers to a function or data to be supplied by an Application
56 ensure that, in the event an Application does not supply the
65 The object code form of an Application may incorporate material from
[all …]
|
| /freebsd/crypto/krb5/src/windows/ |
| H A D | version.rc | 155 #define K5_DESCRIPTION "GSS - GSS Sample Application for " KRB5_PRODUCTNAME_STR "\0"
162 #define K5_DESCRIPTION "Microsoft LSA to MIT Credential Cache Application - " KRB5_PRODUCTNAME_STR …
169 #define K5_DESCRIPTION "MIT to Microsoft LSA Credential Cache Application - " KRB5_PRODUCTNAME_STR …
176 #define K5_DESCRIPTION "Key Version Number Application - " KRB5_PRODUCTNAME_STR "\0"
183 #define K5_DESCRIPTION "Kerberos Change Password Application - " KRB5_PRODUCTNAME_STR "\0"
197 #define K5_DESCRIPTION "Copy Credential Cache Application - " KRB5_PRODUCTNAME_STR "\0"
204 #define K5_DESCRIPTION "Kerberos Copy Ticket Application - " KRB5_PRODUCTNAME_STR "\0"
211 #define K5_DESCRIPTION "Kerberos Delete Ticket Application - " KRB5_PRODUCTNAME_STR "\0"
218 #define K5_DESCRIPTION "Kerberos Destroy Credential Cache Application - " KRB5_PRODUCTNAME_STR "\0"
225 #define K5_DESCRIPTION "Kerberos Initialize Credential Cache Application - " KRB5_PRODUCTNAME_STR "…
[all …]
|
| /freebsd/contrib/elftoolchain/libelf/ |
| H A D | elf_update.3 | 98 .It "Application Controlled Layout"
99 The application can take full control of the layout of the ELF object
105 application-supplied information as below:
134 .Ss Application Supplied Information
135 The application needs to set the following fields in the data
141 application are:
165 If the application is managing the object's layout, it must
168 If the application is managing the object's layout, it must
183 set by the application.
186 application are:
[all …]
|