/netbsd/crypto/external/bsd/openssl/dist/ |
H A D | README-ENGINES.md | 51 form of "control commands". These allow an application to expose to the 53 implementation supports, and for an application to directly feed string 98 pre-compiled application or in your own application code. 114 The recommended way of doing this is for the application to support 116 whatever configuration primitives it might require and the application 123 allows application authors to not get buried in hassle supporting 137 application. It could equally be because the application (or OpenSSL 156 every time application code asks for the 'dynamic' ENGINE, it in fact 158 multiplexes multiple uses of 'dynamic' in a single application in any 181 application authors may have nifty reasons for using it. The "LOAD" [all …]
|
/netbsd/crypto/external/bsd/openssl.old/dist/doc/man3/ |
H A D | SSL_CTX_set_stateless_cookie_generate_cb.pod | 42 L<SSL_stateless(3)> to generate the application-controlled portion of the cookie 50 L<SSL_stateless(3)> to determine whether the application-controlled portion of a 54 including the application-controlled portion, is automatically verified by HMAC 69 integrity of the cookie is not verified by OpenSSL. This is an application
|
H A D | SSL_pending.pod | 19 read by the application via a call to L<SSL_read_ex(3)> or L<SSL_read(3)>. 32 to return 0, even though readable application data bytes are available (because 38 data because the unprocessed buffered data when processed yielded no application 47 SSL_pending() returns the number of buffered and processed application data
|
H A D | RAND_DRBG_set_ex_data.pod | 27 RAND_DRBG_set_ex_data() enables an application to store arbitrary application 31 RAND_DRBG_get_ex_data() retrieves application specific data previously stored
|
H A D | BIO_get_ex_new_index.pod | 16 - application-specific data 39 These functions handle application-specific data for OpenSSL data 57 TYPE_get_ex_data() returns the application data or NULL if an error occurred.
|
H A D | DSA_meth_new.pod | 119 the application's responsibility to free this data before the DSA_METHOD is 124 called in response to the application calling DSA_do_sign() (or DSA_sign()). The 129 will be called in response to the application calling DSA_sign_setup(). The 134 response to the application calling DSA_do_verify() (or DSA_verify()). The 157 called in response to the application calling DSA_new() (if the current default 165 called in response to the application calling DSA_free(). A pointer to the DSA 172 response to the application calling DSA_generate_parameters_ex() (or 178 called in response to the application calling DSA_generate_key(). The parameter
|
H A D | RSA_meth_new.pod | 159 RSA_METHOD. It is the application's responsibility to free this data 164 called in response to the application calling RSA_sign(). The 169 function will be called in response to the application calling 188 be called in response to the application calling RSA_new() (if the 197 This function will be called in response to the application calling 205 function will be called in response to the application calling 211 respectively. This function will be called in response to the application calling 220 These functions will be called in response to the application calling
|
H A D | DH_meth_new.pod | 90 the application's responsibility to free this data before the DH_METHOD is 95 be called in response to the application calling DH_generate_key(). The 100 will be called in response to the application calling DH_compute_key(). The 115 called in response to the application calling DH_new() (if the current default 123 called in response to the application calling DH_free(). A pointer to the DH 130 called in response to the application calling DH_generate_parameters_ex() (or
|
/netbsd/crypto/external/bsd/openssl/dist/doc/man3/ |
H A D | SSL_CTX_set_stateless_cookie_generate_cb.pod | 42 L<SSL_stateless(3)> to generate the application-controlled portion of the cookie 50 L<SSL_stateless(3)> to determine whether the application-controlled portion of a 54 including the application-controlled portion, is automatically verified by HMAC 69 integrity of the cookie is not verified by OpenSSL. This is an application
|
H A D | SSL_pending.pod | 19 read by the application via a call to L<SSL_read_ex(3)> or L<SSL_read(3)>. 32 to return 0, even though readable application data bytes are available (because 38 data because the unprocessed buffered data when processed yielded no application 47 SSL_pending() returns the number of buffered and processed application data
|
H A D | SSL_CTX_set_tmp_dh_callback.pod | 45 DH key inside the server application that is lost when the application 54 As generating DH parameters is extremely time consuming, an application 83 ownership of the B<DH> object is retained by the application. Applications 87 An application may instead specify the DH parameters via a callback function 101 retained by the application and should later be freed.
|
H A D | SSL_set_retry_verify.pod | 16 callback on a client when the application wants to indicate that the handshake 17 should be suspended and the control should be returned to the application. 19 is resumed again by the application, retrying the verification step.
|
H A D | SSL_get_error.pod | 82 may be necessary until progress becomes visible at application 88 again to continue sending the application data. If you get B<SSL_ERROR_WANT_WRITE> 119 The operation did not complete because an application callback set by 122 Details depend on the application. 129 engine is being used. An application can determine whether the engine has 142 through a call to L<ASYNC_init_thread(3)>. The application should retry the 148 The operation did not complete because an application callback set by 151 Details depend on the application.
|
H A D | DSA_meth_new.pod | 126 the application's responsibility to free this data before the DSA_METHOD is 131 called in response to the application calling DSA_do_sign() (or DSA_sign()). The 136 will be called in response to the application calling DSA_sign_setup(). The 141 response to the application calling DSA_do_verify() (or DSA_verify()). The 164 called in response to the application calling DSA_new() (if the current default 172 called in response to the application calling DSA_free(). A pointer to the DSA 179 response to the application calling DSA_generate_parameters_ex() (or 185 called in response to the application calling DSA_generate_key(). The parameter
|
H A D | OSSL_LIB_CTX.pod | 50 new library context to the application library context. The new library context 52 available to it that are available in the application library context (without 53 having to reload them). If the application loads or unloads providers from the 54 application library context then this will be automatically mirrored in the 80 available in the application's library context and therefore will similarly not 83 application's library context and will be similarly mirrored in the child
|
H A D | OPENSSL_ia32cap.pod | 9 env OPENSSL_ia32cap=... <application> 64 For example, in 32-bit application context clearing bit #26 at run-time 67 bank. You might have to do the latter if target OpenSSL application is 70 was exposed to application through OPENSSL_ia32cap_loc(), but not 72 B<OPENSSL_ia32cap> environment variable prior target application start. To
|
H A D | RSA_meth_new.pod | 165 RSA_METHOD. It is the application's responsibility to free this data 170 called in response to the application calling RSA_sign(). The 175 function will be called in response to the application calling 194 be called in response to the application calling RSA_new() (if the 203 This function will be called in response to the application calling 211 function will be called in response to the application calling 217 respectively. This function will be called in response to the application calling 226 These functions will be called in response to the application calling
|
/netbsd/external/bsd/file/dist/magic/magdir/ |
H A D | warc | 8 !:mime application/warc 14 !:mime application/x-ia-arc
|
H A D | sql | 98 # number in the database at offset 60. Later, SQLite added an "application id" 100 # associated application. 106 #!:mime application/x-sqlite3 107 !:mime application/vnd.sqlite3 140 # unknown application ID 142 >>>>68 belong !0 \b, application id %u 213 #!:mime application/x-db-svl-panasonic 215 #!:mime application/x-panasonic-sqlite3
|
H A D | map | 41 !:mime application/x-garmin-map 193 !:mime application/x-garmin-gpm 201 !:mime application/x-garmin-mdr 207 !:mime application/x-garmin-nod 219 !:mime application/x-garmin-net 231 !:mime application/x-garmin-lbl 245 !:mime application/x-garmin-srt 250 !:mime application/x-garmin-tre 272 !:mime application/x-garmin-trf 282 !:mime application/x-garmin-typ [all …]
|
H A D | webassembly | 7 # the MIME type is application/wasm. 15 !:mime application/wasm
|
H A D | fsav | 52 !:mime application/x-clamav-database 66 !:mime application/x-clamav 114 !:mime application/x-avira-qua 115 #!:mime application/octet-stream
|
/netbsd/external/bsd/unbound/dist/libunbound/python/doc/examples/ |
H A D | index.rst | 6 an application, as a library where can answer DNS queries for the application.
|
/netbsd/external/bsd/ntp/dist/ |
H A D | readme.y2kfixes | 5 This is the "readme" file for the freeware application which has 17 for what AT&T Labs considers an "application". 48 information. If integrated with the original application items 50 distributed on the same media as the original application there 90 appropriate to the application, to provide the exact snapshots.
|
/netbsd/external/bsd/openpam/dist/ |
H A D | RELNOTES | 14 application (su) which demonstrate how to use the PAM library. 16 - A test application (pamtest) which can be used to test policies and
|