Home
last modified time | relevance | path

Searched full:responder (Results 1 – 25 of 179) sorted by relevance

12345678

/freebsd/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 …]
/freebsd/secure/usr.bin/openssl/man/
H A Dopenssl-ocsp.1176 to an OCSP responder and behave like a mini OCSP server itself.
249 Specify the responder host and optionally port and path via a URL.
284 that is sent to the responder.
288 Connection timeout to the OCSP responder in seconds.
289 On POSIX systems, when running as an OCSP responder, this option also limits
290 the time that the responder is willing to wait for the client request.
291 This time is measured from the time the responder accepts the connection until
305 when the complete responder certificate chain is not available or trusting a
309 File or URI containing explicitly trusted responder certificates.
351 seconds. In practice the OCSP responder and clients clocks may not be precisely
[all …]
/freebsd/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
/freebsd/secure/lib/libcrypto/man/man3/
H A DOSSL_PARAM.3101 calls some function (the \fIresponder\fR) that has intimate knowledge
119 However, if the \fIresponder\fR can handle multiple elements with the
239 \&\fIdata_size\fR is not relevant. However, the \fIresponder\fR will set
264 \&\fIdata_size\fR is not relevant. However, the \fIresponder\fR will set
277 Keys that a \fIsetter\fR or \fIresponder\fR doesn't recognise should simply
284 Apart from the \fIreturn_size\fR, a \fIresponder\fR must never change the fields
299 \&\fBOSSL_PARAM_UTF8_STRING\fR is NULL, the \fIresponder\fR should
301 and return success. Later the responder will be called again
304 If a \fIresponder\fR finds that some data sizes are too small for the
310 \&\fBOSSL_PARAM_INTEGER\fR), a \fIresponder\fR may choose to return an error
[all …]
H A DOCSP_sendreq_new.373 \&\- OCSP responder query functions
111 For example if the responder URL is \f(CW\*(C`http://example.com/ocspreq\*(C'\fR the BIO
159 responder or NULL if an error occurred.
H A DOCSP_resp_find_status.3159 \&\fBOCSP_resp_get0_id()\fR gets the responder id of \fIbs\fR. If the responder ID is
161 responder ID is by key ID then \fI*pid\fR is set to the key ID and \fI*pname\fR
178 in \fIcerts\fR. It then searches the certificates the responder may have included
H A DOCSP_response_status.3111 subject name in the supplied X509 certificate \fIcert\fR for the OCSP responder.
114 key in the supplied X509 certificate \fIcert\fR for the OCSP responder. The key is
138 \&\fIflags\fR option \fIOCSP_RESPID_KEY\fR is set then the responder is identified by key ID
/freebsd/sys/contrib/dev/iwlwifi/fw/api/
H A Dlocation.h44 * @TOF_RESPONDER_CONFIG_CMD: FTM responder configuration, one of
71 * @TOF_RESPONDER_STATS: FTM responder statistics notification,
143 * enum iwl_tof_responder_cmd_valid_field - valid fields in the responder cfg
194 * enum iwl_tof_responder_cfg_flags - responder configuration flags
454 * struct iwl_tof_responder_dyn_config_cmd_v2 - Dynamic responder settings
486 * struct iwl_tof_responder_dyn_config_cmd - Dynamic responder settings
566 * 1: Initiator interact with Responder machine: need to send the
567 * Initiator Acks with HT 40MHz / 80MHz, since the Responder should
569 * configure the opposite machine to be Responder).
598 * enum iwl_initiator_ap_flags - per responder FTM configuration flags
[all …]
/freebsd/contrib/wpa/src/pasn/
H A Dpasn_common.h2 * PASN info for initiator and responder
52 /* Responder */
119 /* Responder */
174 /* Responder */
209 /* Responder */
/freebsd/sbin/ping/
H A Dping.8452 requests unicast addresses from all of the responder's interfaces.
455 responder's address are requests.
457 requests responder's IPv4-compatible and IPv4-mapped addresses.
459 requests responder's global-scope addresses.
461 requests responder's site-local addresses.
463 requests responder's link-local addresses.
465 requests responder's anycast addresses.
466 Without this character, the responder will return unicast addresses only.
467 With this character, the responder will return anycast addresses only.
468 Note that the specification does not specify how to get responder's
/freebsd/contrib/wpa/src/common/
H A Ddpp_auth.c92 /* Responder Bootstrapping Key Hash */ in dpp_auth_build_req()
277 /* Responder Bootstrapping Key Hash */ in dpp_auth_build_resp()
283 /* Responder Protocol Key */ in dpp_auth_build_resp()
1038 /* Responder Bootstrapping Key Hash */ in dpp_auth_build_conf()
1319 "DPP: Responder reported incompatible roles"); in dpp_auth_resp_rx_status()
1322 "DPP: Responder reported more time needed"); in dpp_auth_resp_rx_status()
1325 "DPP: Responder reported failure (status %d)", in dpp_auth_resp_rx_status()
1327 dpp_auth_fail(auth, "Responder reported failure"); in dpp_auth_resp_rx_status()
1456 "Missing or invalid required Responder Bootstrapping Key Hash attribute"); in dpp_auth_resp_rx()
1459 wpa_hexdump(MSG_DEBUG, "DPP: Responder Bootstrapping Key Hash", in dpp_auth_resp_rx()
[all …]
/freebsd/crypto/openssl/apps/
H A Docsp.c121 OPT_SECTION("Responder"),
123 "Connection timeout (in seconds) to the OCSP responder"},
127 {"multi", OPT_MULTI, 'p', "run multiple responder processes"},
144 "Responder certificate to sign responses with"},
145 {"rkey", OPT_RKEY, '<', "Responder key to sign responses with"},
146 {"passin", OPT_PASSIN, 's', "Responder key pass phrase source"},
155 {"url", OPT_URL, 's', "Responder URL"},
157 {"port", OPT_PORT, 'N', "Port to run responder on"},
585 rsigner = load_cert(rsignfile, FORMAT_UNDEF, "responder certificate"); in ocsp_main()
587 BIO_printf(bio_err, "Error loading responder certificate\n"); in ocsp_main()
[all …]
/freebsd/crypto/heimdal/lib/hx509/
H A Dtest_chain.in120 echo "ocsp non-ca responder"
126 echo "ocsp ca responder"
132 echo "ocsp no-ca responder, missing cert"
138 echo "ocsp no-ca responder, missing cert, in pool"
143 chain:FILE:$srcdir/data/ocsp-responder.crt > /dev/null || exit 1
145 echo "ocsp no-ca responder, keyHash"
/freebsd/crypto/openssl/demos/certs/
H A Docsprun.sh7 # Example of running an querying OpenSSL test OCSP responder.
16 # Run OCSP responder.
H A DREADME.txt14 The script ocsprun.sh runs the test responder on port 8888 covering the
18 test responder.
H A Docspquery.sh3 # Example querying OpenSSL test responder. Assumes ocsprun.sh has been
15 # Send responder queries for each certificate.
H A Dmkcerts.sh43 # OCSP responder certificate: request first
44 CN="Test OCSP Responder Cert" opensslcmd req -config ca.cnf -nodes \
46 # Sign using intermediate CA and responder extensions
/freebsd/lib/libgssapi/
H A Dgssapi.369 the context initiator is authenticated to the responder,
70 and may require that the responder is authenticated in turn.
71 The initiator may optionally give the responder the right to initiate
77 but which may be used by the responder.
/freebsd/sys/contrib/device-tree/Bindings/fsi/
H A Dibm,i2cr-fsi-master.yaml7 title: IBM I2C Responder virtual FSI master
13 The I2C Responder (I2CR) is a an I2C device that's connected to an FSI CFAM
/freebsd/contrib/lib9p/
H A Dthreadpool.h57 * All workers, including the responder, use this as their
59 * responder is that it runs different code and waits on the
81 L9P_WS_REPLYING, /* responder is in final reply path */
H A Dthreadpool.c103 /* move to responder queue, updating work-state */ in l9p_worker()
109 /* signal the responder */ in l9p_worker()
201 pthread_set_name_np(worker->ltw_thread, "9p-responder"); in l9p_threadpool_init()
211 /* need the one responder, and at least one worker */ in l9p_threadpool_init()
376 * will get queued for reply later, when the responder in l9p_threadpool_tflush()
/freebsd/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()

12345678