/openbsd/gnu/llvm/lldb/third_party/Python/module/pexpect-4.6/pexpect/ |
H A D | run.py | 103 responses = [y for x,y in events] 106 responses = list(events.values()) 110 responses = None 122 if isinstance(responses[index], child.allowed_string_types): 123 child.send(responses[index]) 124 elif (isinstance(responses[index], types.FunctionType) or 125 isinstance(responses[index], types.MethodType)): 126 callback_result = responses[index](locals()) 135 .format(index=index, value=responses[index]))
|
/openbsd/usr.bin/ssh/ |
H A D | auth-bsdauth.c | 93 bsdauth_respond(void *ctx, u_int numresponses, char **responses) in bsdauth_respond() argument 107 authok = auth_userresponse(authctxt->as, responses[0], 0); in bsdauth_respond() 109 debug3("bsdauth_respond: <%s> = <%d>", responses[0], authok); in bsdauth_respond()
|
H A D | auth.h | 122 int (*respond)(void *ctx, u_int numresp, char **responses);
|
H A D | PROTOCOL.mux | 16 facilitate matching of responses to requests. 18 Many multiplexing (mux) client requests yield immediate responses from
|
H A D | monitor_wrap.c | 796 mm_bsdauth_respond(void *ctx, u_int numresponses, char **responses) in mm_bsdauth_respond() argument 807 if ((r = sshbuf_put_cstring(m, responses[0])) != 0) in mm_bsdauth_respond()
|
/openbsd/lib/libcrypto/ocsp/ |
H A D | ocsp_srv.c | 157 if (!rsp->tbsResponseData->responses && in OCSP_basic_add1_status() 158 !(rsp->tbsResponseData->responses = sk_OCSP_SINGLERESP_new_null())) in OCSP_basic_add1_status() 206 if (!(sk_OCSP_SINGLERESP_push(rsp->tbsResponseData->responses, single))) in OCSP_basic_add1_status()
|
H A D | ocsp_prn.c | 261 for (i = 0; i < sk_OCSP_SINGLERESP_num(rd->responses); i++) { in OCSP_RESPONSE_print() 262 if (! sk_OCSP_SINGLERESP_value(rd->responses, i)) in OCSP_RESPONSE_print() 264 single = sk_OCSP_SINGLERESP_value(rd->responses, i); in OCSP_RESPONSE_print()
|
H A D | ocsp_cl.c | 234 return sk_OCSP_SINGLERESP_num(bs->tbsResponseData->responses); in OCSP_resp_count() 244 return sk_OCSP_SINGLERESP_value(bs->tbsResponseData->responses, idx); in OCSP_resp_get0() 317 sresp = bs->tbsResponseData->responses; in OCSP_resp_find()
|
H A D | ocsp_local.h | 218 STACK_OF(OCSP_SINGLERESP) *responses;
|
H A D | ocsp_vfy.c | 254 sresp = bs->tbsResponseData->responses; in ocsp_check_issuer()
|
/openbsd/gnu/usr.bin/cvs/doc/ |
H A D | cvsclient.info-1 | 75 `Valid-responses' mechanism (*note Protocol::), which is more flexible. 109 responses), and then waits for the server to send back all 110 responses (without waiting for further client requests). This has 189 server responses (each of which is followed by a linefeed) are the 207 Typically the server will provide a series of `E' responses 243 complete, the server continues with the responses described above 304 horizontal tab; "requests" are what the client sends and "responses" 311 `Valid-responses' request, containing all the responses it supports, 335 * Response pathnames:: The "pathname" in responses 336 * Responses:: List of responses [all …]
|
H A D | cvsclient.info-2 | 27 before any requests other than `Valid-responses', 31 `Valid-responses REQUEST-LIST \n' 32 Response expected: no. Tell the server what responses the client 88 each of the responses, so one can use the repository from whichever 336 the server is sending responses. The FILENAME is a file within 583 responses, and (2) the `expand-modules' request. 700 `Checked-in' responses from the buggy servers. 769 responses. 797 Any set of responses always ends with `error' or `ok'. This 800 The responses `Checked-in', `New-entry', `Updated', `Created', [all …]
|
H A D | cvsclient.texi | 313 @code{Valid-responses} request, containing all the responses it 550 @item Valid-responses @var{request-list} \n 744 responses. 879 responses. 1273 @code{Checked-in} responses from the buggy servers. 1311 errors, pending @code{Notified} responses, etc. 1388 @section The "pathname" in responses 1435 Here are the responses: 1705 @var{data} of other tagged text responses). 1745 responses might be sent as: [all …]
|
H A D | cvsclient.info-3 | 15 Here are the responses: 143 `Valid-responses' request). 216 responses. PATHNAME should be used to look and see whether some 231 (extensions should be done with new responses, not by extending 232 this one, for graceful handling of `Valid-responses'). 315 responses might be sent as: 333 print an error message with `MT' responses, and then issue a 360 `Update-existing' responses, but we don't try to specify here whether 393 protocol negotiation. In actual practice the lists of valid responses 397 C: Valid-responses ok error Checked-in M E [all …]
|
H A D | cvsclient.aux | 46 'xrdef {Response pathnames-title}{The "pathname" in responses}
|
/openbsd/usr.sbin/unbound/doc/ |
H A D | TODO | 4 will result in proper negative responses. 53 of responses over a time interval is collected, and each is validated. 73 [2] more logging about stuff like SERVFAIL and REFUSED responses
|
H A D | CREDITS | 21 Daisuke HIGASHI - patch for rrset-roundrobin and minimal-responses.
|
H A D | example.conf.in | 226 # the time to live (TTL) value cap for negative responses in the cache 230 # For negative responses in the cache. If disabled, default, 238 # minimum wait time for responses, increase if uplink is long. In msec. 241 # maximum wait time for responses. In msec. 622 # minimal-responses: yes 720 # Limit serving of expired responses to configured seconds after 913 # Pad responses to padded queries received over TLS 914 # pad-responses: yes 917 # pad-responses-block-size: 468 1052 # Enable to attach Extended DNS Error codes (RFC8914) to responses. [all …]
|
H A D | control_proto_spec.txt | 27 Queries and responses
|
/openbsd/gnu/usr.bin/cvs/src/ |
H A D | client.h | 179 extern struct response responses[];
|
/openbsd/gnu/usr.bin/perl/ |
H A D | SECURITY.md | 21 of your email client when you send subsequent responses so that the
|
/openbsd/sbin/unwind/libunbound/util/ |
H A D | configlexer.lex | 464 minimal-responses{COLON} { YDVAR(1, VAR_MINIMAL_RESPONSES) } 555 pad-responses{COLON} { YDVAR(1, VAR_PAD_RESPONSES) } 556 pad-responses-block-size{COLON} { YDVAR(1, VAR_PAD_RESPONSES_BLOCK_SIZE) }
|
/openbsd/usr.sbin/unbound/util/ |
H A D | configlexer.lex | 464 minimal-responses{COLON} { YDVAR(1, VAR_MINIMAL_RESPONSES) } 555 pad-responses{COLON} { YDVAR(1, VAR_PAD_RESPONSES) } 556 pad-responses-block-size{COLON} { YDVAR(1, VAR_PAD_RESPONSES_BLOCK_SIZE) }
|
/openbsd/usr.sbin/nsd/doc/ |
H A D | README | 238 --disable-minimal-responses 240 Disable minimal responses. If disabled, responses are more likely 242 NSD will leave out RRsets to make responses fit inside one datagram, 243 but for shorter responses the full normal response is carried. 742 improves performance, and ensures responses written to the socket are pushed
|
/openbsd/usr.sbin/nsd/ |
H A D | nsd.conf.sample.in | 52 # care must be taken to ensure responses go out the same interface the 201 # minimal-responses only emits extra data for referrals. 202 # minimal-responses: no
|