Searched refs:challenges (Results 1 – 9 of 9) sorted by relevance
682 cs->challenges[i] = NULL; in init_http_auth_challenges()692 if (cs->challenges[i] != NULL) { in clean_http_auth_challenges()694 free(cs->challenges[i]); in clean_http_auth_challenges()777 cs->challenges[cs->count] = in http_parse_authenticate()816 cs->challenges[cs->count]->realm = in http_parse_authenticate()819 cs->challenges[cs->count]->qop = in http_parse_authenticate()822 cs->challenges[cs->count]->nonce = in http_parse_authenticate()825 cs->challenges[cs->count]->opaque = in http_parse_authenticate()828 cs->challenges[cs->count]->algo = in http_parse_authenticate()831 cs->challenges[cs->count]->stale = in http_parse_authenticate()[all …]
29 public key that is used to sign challenges. In OpenSSH, ssh-keygen
7827 upstream: Restrict ssh-agent from signing web challenges for FIDO7837 attached granting the ability for the remote side to sign challenges7840 Note that the converse case of web browsers signing SSH challenges is
219 challenges have a par subtype, as in the IFF challenge IFFpar, while
142 challenges, each a tuple matching the prototype:
88 Indicate support for extended responses in challenges and check for such
2278 * added support for EAP-SIM with two challenges2279 (phase1="sim_min_num_chal=3" can be used to require three challenges)
605 - Only remember {WWW,Proxy}-Authenticate "Basic" challenges; no
2237 challenges, but nothing insurmountable. This recipe shows you how you can do it.