Home
last modified time | relevance | path

Searched refs:responder (Results 1 – 25 of 37) sorted by relevance

12

/src/crypto/openssl/doc/man1/
H A Dopenssl-ocsp.pod.in84 to an OCSP responder and behave like a mini OCSP server itself.
173 Specify the responder host and optionally port and path via a URL.
212 that is sent to the responder.
217 Connection timeout to the OCSP responder in seconds.
218 On POSIX systems, when running as an OCSP responder, this option also limits
219 the time that the responder is willing to wait for the client request.
220 This time is measured from the time the responder accepts the connection until
236 when the complete responder certificate chain is not available or trusting a
241 File or URI containing explicitly trusted responder certificates.
291 seconds. In practice the OCSP responder and clients clocks may not be precisely
[all …]
H A Dopenssl-s_server.pod.in523 Sets a fallback responder URL to use if no responder URL is present in the
525 certificate does not contain a responder address.
531 Overrides any OCSP responder URLs from the certificate and always provides the
/src/crypto/openssl/doc/man3/
H A DOSSL_PARAM.pod44 calls some function (the I<responder>) that has intimate knowledge
59 I<responder>.
64 However, if the I<responder> can handle multiple elements with the
126 I<responder> must set this field to indicate size of the parameter
129 I<responder> must still set this field to indicate the minimum data
195 I<data_size> is not relevant. However, the I<responder> will set
221 I<data_size> is not relevant. However, the I<responder> will set
241 Keys that a I<setter> or I<responder> doesn't recognise should simply
252 Apart from the I<return_size>, a I<responder> must never change the fields
271 B<OSSL_PARAM_UTF8_STRING> is NULL, the I<responder> should
[all …]
H A DOCSP_sendreq_new.pod14 - OCSP responder query functions
50 For example if the responder URL is C<http://example.com/ocspreq> the BIO
95 responder or NULL if an error occurred.
H A DOCSP_response_status.pod52 subject name in the supplied X509 certificate I<cert> for the OCSP responder.
55 key in the supplied X509 certificate I<cert> for the OCSP responder. The key is
79 I<flags> option I<OCSP_RESPID_KEY> is set then the responder is identified by key ID
H A DOCSP_resp_find_status.pod100 OCSP_resp_get0_id() gets the responder id of I<bs>. If the responder ID is
102 responder ID is by key ID then I<*pid> is set to the key ID and I<*pname>
119 in I<certs>. It then searches the certificates the responder may have included
H A DSSL_get_certificate.pod47 example for the purpose of identifying a certificate's OCSP responder URL so
H A DOCSP_cert_to_id.pod66 the other functions are used by responder applications.
H A DOCSP_REQUEST_new.pod97 /* Do something with req, e.g. query responder */
H A DOCSP_request_add1_nonce.pod62 this will happen if the responder doesn't support nonces. A zero return value
H A DOSSL_PARAM_int.pod341 to a I<responder>, i.e. to get parameter data back.
381 A I<responder> that receives this array (as C<params> in this example)
H A DX509_STORE_CTX_get_error.pod441 recognized by the OCSP responder.
/src/crypto/openssl/demos/certs/
H A DREADME.txt14 The script ocsprun.sh runs the test responder on port 8888 covering the
18 test responder.
H A Dca.cnf44 # OCSP responder certificate
/src/crypto/krb5/src/lib/krb5/krb/
H A Dgic_opt.c29 krb5_responder_fn responder; member
438 krb5_responder_fn responder, void *data) in krb5_get_init_creds_opt_set_responder() argument
444 opte->responder = responder; in krb5_get_init_creds_opt_set_responder()
459 *responder_out = opte->responder; in k5_gic_opt_get_responder()
H A Dpreauth2.c975 krb5_responder_fn responder; in k5_preauth() local
1011 k5_gic_opt_get_responder(ctx->opt, &responder, &responder_data); in k5_preauth()
1012 if (responder != NULL && !k5_response_items_empty(ctx->rctx.items)) { in k5_preauth()
1013 ret = (*responder)(context, responder_data, &ctx->rctx); in k5_preauth()
H A Dget_in_tkt.c53 krb5_responder_fn responder; in decrypt_as_reply() local
96 k5_gic_opt_get_responder(ctx->opt, &responder, &responder_data); in decrypt_as_reply()
97 if (responder != NULL) { in decrypt_as_reply()
108 ret = (*responder)(context, responder_data, &ctx->rctx); in decrypt_as_reply()
/src/contrib/unbound/dnstap/
H A Ddnstap.proto244 // The network address of the message responder.
253 // The transport port of the message responder.
283 // The responder's original wire-format DNS response message, verbatim.
/src/crypto/heimdal/lib/hx509/
H A Docsp.asn172 OCSPKeyHash ::= OCTET STRING --SHA-1 hash of responder's public key
H A DMakefile.am378 data/ocsp-responder.crt \
379 data/ocsp-responder.key \
H A Dtest_chain.in143 chain:FILE:$srcdir/data/ocsp-responder.crt > /dev/null || exit 1
/src/sys/modules/iwlwifi/
H A DMakefile34 SRCS+= mvm/ftm-initiator.c mvm/ftm-responder.c mvm/fw.c
/src/crypto/openssl/doc/man7/
H A DEVP_KDF-X942-ASN1.pod58 An optional octet string containing public info contributed by the responder.
/src/crypto/krb5/src/include/krb5/
H A Dkrb5.hin6495 * Long-term password responder question
6505 * OTP responder question
6507 * The OTP responder question is asked when the KDC indicates that an OTP
6568 * this flag is not set, the responder may either concatenate PIN + token value
6575 * PKINIT responder question
6577 * The PKINIT responder question is asked when the client needs a password
6621 * A responder context is supplied by the krb5 authentication system to a
6623 * answers. Questions contained in a responder context can be listed using
6634 * List the question names contained in the responder context.
6651 * Retrieve the challenge data for a given question in the responder context.
[all …]
/src/crypto/openssl/doc/internal/man3/
H A Dossl_provider_new.pod263 responder.

12