| /external/chromium_org/chrome/browser/chromeos/attestation/ |
| attestation_signed_data.proto | 11 // The message used by the attestation service for challenge response.
|
| /external/chromium_org/net/http/ |
| http_auth_challenge_tokenizer.h | 15 // Breaks up a challenge string into the the auth scheme and parameter list,
17 // challenge = auth-scheme 1*SP 1#auth-param
19 // Depending on the challenge scheme, it may be appropriate to interpret the
33 // Get the auth scheme of the challenge.
|
| http_auth.cc | 36 // Choose the challenge whose authentication handler gives the maximum score.
47 << ErrorToString(rv) << " Challenge: " << cur_challenge;
74 std::string challenge; local
77 while (headers->EnumerateHeader(&iter, header_name, &challenge)) {
78 HttpAuthChallengeTokenizer props(challenge.begin(), challenge.end());
83 *challenge_used = challenge;
|
| http_auth_sspi_win_unittest.cc | 66 HttpAuthChallengeTokenizer challenge(challenge_text.begin(),
69 auth_sspi.ParseChallenge(&challenge));
97 // If the first round challenge has an additional authentication token, it
98 // should be treated as an invalid challenge from the server.
103 HttpAuthChallengeTokenizer challenge(challenge_text.begin(),
106 auth_sspi.ParseChallenge(&challenge));
110 // If a later-round challenge is simply "Negotiate", it should be treated as
111 // an authentication challenge rejection from the server or proxy.
132 // If a later-round challenge has an invalid base64 encoded token, it should
133 // be treated as an invalid challenge
[all...] |
| http_auth_handler_mock.h | 46 HttpAuthChallengeTokenizer* challenge,
91 HttpAuthChallengeTokenizer* challenge) OVERRIDE;
97 virtual bool Init(HttpAuthChallengeTokenizer* challenge) OVERRIDE;
|
| http_auth_handler_unittest.cc | 22 std::string challenge = "Mock asdf"; local
39 challenge.begin(), challenge.end());
|
| http_auth.h | 52 AUTHORIZATION_RESULT_INVALID, // The authentication challenge headers are
59 // with the new challenge
110 // Get the name of the header containing the auth challenge
125 // Iterate through the challenge headers, and pick the best one that
126 // we support. Obtains the implementation class for handling the challenge,
127 // and passes it back in |*handler|. If no supported challenge was found,
147 // rejection of the previous challenge, except in the Digest case when a
155 // |target| specifies whether the authentication challenge response came
160 // |challenge_used| is the text of the authentication challenge used in
|
| http_auth_handler_factory.cc | 23 const std::string& challenge,
28 HttpAuthChallengeTokenizer props(challenge.begin(), challenge.end());
34 const std::string& challenge,
40 HttpAuthChallengeTokenizer props(challenge.begin(), challenge.end());
176 HttpAuthChallengeTokenizer* challenge,
183 std::string scheme = challenge->scheme();
195 return it->second->CreateAuthHandler(challenge, target, origin, reason,
|
| /frameworks/base/obex/javax/obex/ |
| ObexSession.java | 55 * Called when the server received an authentication challenge header. This
56 * will cause the authenticator to handle the authentication challenge.
57 * @param header the header with the authentication challenge
68 * An authentication challenge is made up of one required and two
70 * the authentication challenge and it represents the challenge digest
76 byte[] challenge = ObexHelper.getTagValue((byte)0x00, header.mAuthChall);
150 * will be sent. The second optional tag is 0x02 and is the challenge
163 byte[] digest = new byte[challenge.length + password.length + 1];
164 System.arraycopy(challenge, 0, digest, 0, challenge.length)
[all...] |
| Authenticator.java | 36 * This interface provides a way to respond to authentication challenge and
38 * authentication challenge or authentication response header, the
49 * When a client or server receives an authentication challenge header, the
54 * the 16-byte challenge received in the authentication challenge is combined
73 * challenge sent via the authentication challenge, apply the MD5 hash
86 * Called when a client or a server receives an authentication challenge
87 * header. It should respond to the challenge with a
89 * and password for the challenge
[all...] |
| /external/ppp/pppd/ |
| chap-md5.c | 59 unsigned char *challenge, unsigned char *response,
67 challenge_len = *challenge++;
70 /* Generate hash of ID, secret, challenge */
74 MD5_Update(&ctx, challenge, challenge_len);
89 unsigned char *challenge, char *secret, int secret_len,
94 int challenge_len = *challenge++;
99 MD5_Update(&ctx, challenge, challenge_len);
|
| chap_ms.c | 154 { "mschap-challenge", o_string, &mschap_challenge,
155 "specify CHAP challenge" },
156 { "mschap2-peer-challenge", o_string, &mschap2_peer_challenge,
157 "specify CHAP peer challenge" },
163 * chapms_generate_challenge - generate a challenge for MS-CHAP.
164 * For MS-CHAP the challenge length is fixed at 8 bytes.
165 * The length goes in challenge[0] and the actual challenge starts
166 * at challenge[1].
169 chapms_generate_challenge(unsigned char *challenge)
[all...] |
| chap-new.c | 51 /* Hook for a plugin to validate CHAP challenge */
54 unsigned char *challenge, unsigned char *response,
70 { "chap-max-challenge", o_int, &chap_max_transmits,
71 "Set max #xmits for challenge", OPT_PRIO },
88 * These limits apply to challenge and response packets we send.
101 unsigned char challenge[CHAL_MAX_PKTLEN]; member in struct:chap_server_state
124 unsigned char *challenge, unsigned char *response,
226 * There isn't much to do until we receive a challenge.
251 * chap_timeout - It's time to send another challenge to the peer.
252 * This could be either a retransmission of a previous challenge,
[all...] |
| /external/chromium_org/net/base/ |
| keygen_handler_unittest.cc | 57 768, "some challenge", GURL("http://www.example.com")));
73 // Assert that |result| is a valid output for KeygenHandler given challenge
74 // string of |challenge|.
76 const std::string& challenge) {
100 // Challenge String: some challenge
114 AssertValidSignedPublicKeyAndChallenge(result, "some challenge");
117 void ConcurrencyTestCallback(const std::string& challenge,
150 "some challenge",
164 AssertValidSignedPublicKeyAndChallenge(results[i], "some challenge");
[all...] |
| /external/chromium_org/ppapi/c/private/ |
| ppb_platform_verification_private.h | 68 * Requests a platform challenge for a given service id.
71 * <code>PP_VARTYPE_STRING</code> containing the service_id for the challenge.
73 * @param[in] challenge A <code>PP_Var</code> of type
74 * <code>PP_VARTYPE_ARRAY_BUFFER</code> that contains the challenge data.
89 * the platform challenge has been completed. This callback will only run if
96 struct PP_Var challenge,
|
| /external/wpa_supplicant_8/src/eap_server/ |
| eap_server_md5.c | 20 u8 challenge[CHALLENGE_LEN]; member in struct:eap_md5_data
50 if (random_get_bytes(data->challenge, CHALLENGE_LEN)) {
66 wpabuf_put_data(req, data->challenge, CHALLENGE_LEN);
67 wpa_hexdump(MSG_MSGDUMP, "EAP-MD5: Challenge", data->challenge,
123 data->challenge, CHALLENGE_LEN, hash)) {
|
| /external/google-tv-pairing-protocol/cpp/src/polo/pairing/ |
| clientpairingsession.h | 33 // @param challenge the challenge
38 PoloChallengeResponse* challenge,
|
| serverpairingsession.h | 33 // @param challenge the challenge response
37 PoloChallengeResponse* challenge,
|
| /external/chromium_org/chrome/browser/resources/cryptotoken/ |
| gnubby-u2f.js | 38 * @param {ArrayBuffer|Uint8Array} challenge Enrollment challenge
44 Gnubby.prototype.enroll = function(challenge, appIdHash, cb,
55 challenge.length + appIdHash.length]);
56 var u8 = new Uint8Array(apdu.length + challenge.length +
59 for (var i = 0; i < challenge.length; ++i) u8[i + apdu.length] =
60 challenge[i];
62 u8[i + apdu.length + challenge.length] = appIdHash[i];
68 * @param {ArrayBuffer|Uint8Array} challengeHash Hashed signature challenge
|
| usbsignhandler.js | 96 var challenge = signResult['challenge'];
98 this.notifySuccess_(gnubby, challenge, info);
114 * @param {SignHelperChallenge} challenge Challenge signed
118 UsbSignHandler.prototype.notifySuccess_ = function(gnubby, challenge, info) {
131 'appIdHash': B64_encode(challenge['appIdHash']),
132 'challengeHash': B64_encode(challenge['challengeHash']),
133 'keyHandle': B64_encode(challenge['keyHandle']),
|
| singlesigner.js | 7 * signing each challenge in an array of challenges until a success condition
18 * challenge: (SignHelperChallenge|undefined),
26 * operation using each challenge in an array of challenges until its success
31 * For enroll, success is defined as each challenge yielding wrong data. This
33 * challenge.
35 * For sign, success is defined as any challenge yielding ok.
89 /** The signer is currently signing a challenge. */
266 * @param {number} challengeIndex Index of challenge to sign
294 var challenge = this.challenges_[challengeIndex];
295 var challengeHash = challenge.challengeHash
[all...] |
| /external/chromium_org/ppapi/cpp/private/ |
| platform_verification.h | 22 const Var& challenge,
|
| /external/chromium_org/ppapi/thunk/ |
| ppb_platform_verification_api.h | 23 const PP_Var& challenge,
|
| /external/nist-sip/java/gov/nist/javax/sip/clientauthutils/ |
| AuthenticationHelper.java | 30 * the specified Response (Challenge) and appends it to the challenged
35 * @param challenge
36 * the 401/407 challenge response
55 public abstract ClientTransaction handleChallenge(Response challenge,
|
| package.html | 2 This package contains a set of utilities for client side Authentication Challenge handling. It has been
|
