Home
last modified time | relevance | path

Searched refs:Challenge (Results 1 – 25 of 30) sorted by relevance

12

/netbsd/src/external/bsd/ppp/dist/pppd/
Dcrypto_ms.c193 unsigned char Challenge[8] = { in test_encrypt() local
210 DesEncrypt(Challenge, ZPasswordHash + 0, response + 0); in test_encrypt()
211 DesEncrypt(Challenge, ZPasswordHash + 7, response + 8); in test_encrypt()
212 DesEncrypt(Challenge, ZPasswordHash + 14, response + 16); in test_encrypt()
219 unsigned char Challenge[8] = { in test_decrypt() local
237 failure += memcmp(Challenge, Output, sizeof(Challenge)); in test_decrypt()
241 failure += memcmp(Challenge, Output, sizeof(Challenge)); in test_decrypt()
245 failure += memcmp(Challenge, Output, sizeof(Challenge)); in test_decrypt()
Dchap_ms.c538 char *username, u_char Challenge[8]) in ChallengeHash()
566 BCOPY(hash, Challenge, 8); in ChallengeHash()
633 u_char Challenge[8]; in ChapMS2_NT() local
635 ChallengeHash(PeerChallenge, rchallenge, username, Challenge); in ChapMS2_NT()
641 ChallengeResponse(Challenge, PasswordHash, NTResponse); in ChapMS2_NT()
694 u_char Challenge[8]; in GenerateAuthenticatorResponse() local
716 ChallengeHash(PeerChallenge, rchallenge, username, Challenge); in GenerateAuthenticatorResponse()
725 if (PPP_DigestUpdate(ctx, Challenge, sizeof(Challenge))) { in GenerateAuthenticatorResponse()
/netbsd/src/external/bsd/wpa/dist/wpa_supplicant/
Deap_testing.txt142 - EAP-MD5-Challenge
148 - EAP-PEAPv0 / MD5-Challenge
150 - EAP-TTLS / EAP-MD5-Challenge
180 - EAP-TTLS / EAP-MD5-Challenge (using FreeRADIUS as inner auth srv)
185 - EAP-MD5-Challenge
188 - EAP-PEAP / MD5-Challenge
192 - EAP-MD5-Challenge
207 - EAP-TTLS / EAP-MD5-Challenge
212 - EAP-MD5-Challenge
219 - EAP-PEAPv0 / MD5-Challenge
[all …]
DREADME63 * EAP-PEAP/MD5-Challenge (both PEAPv0 and PEAPv1)
64 * EAP-TTLS/EAP-MD5-Challenge
86 * EAP-MD5-Challenge
574 3) EAP-TTLS/EAP-MD5-Challenge configuration with anonymous identity for the
744 CTRL-REQ-OTP-2:Challenge 1235663 needed for SSID foobar
DChangeLog1590 processed after AKA Challenge response has been sent
2474 EAP-TTLS/EAP-MD5-Challenge
2484 EAP-PEAP/MD5-Challenge
/netbsd/src/sys/arch/sgimips/
DREADME.IPn17 IP19 Challenge L/XL, Onyx Everest
19 IP21 Power Challenge R8K, Power Onyx Everest
20 IP22 Indigo2, Challenge M Fullhouse
21 IP24 (IP22) Indy, Challenge S Guinness
22 IP25 Power Challenge R10K Everest
/netbsd/src/external/bsd/tcpdump/dist/tests/
Deapon1-v-nosmb.out74 Type SIM (18) subtype [Challenge] 0x0b
76 Type SIM (18) subtype [Challenge] 0x0b
135 Type SIM (18) subtype [Challenge] 0x0b
137 Type SIM (18) subtype [Challenge] 0x0b
191 Type SIM (18) subtype [Challenge] 0x0b
195 Type SIM (18) subtype [Challenge] 0x0b
326 Type SIM (18) subtype [Challenge] 0x0b
328 Type SIM (18) subtype [Challenge] 0x0b
Deapon1-v.out74 Type SIM (18) subtype [Challenge] 0x0b
76 Type SIM (18) subtype [Challenge] 0x0b
135 Type SIM (18) subtype [Challenge] 0x0b
137 Type SIM (18) subtype [Challenge] 0x0b
191 Type SIM (18) subtype [Challenge] 0x0b
195 Type SIM (18) subtype [Challenge] 0x0b
326 Type SIM (18) subtype [Challenge] 0x0b
328 Type SIM (18) subtype [Challenge] 0x0b
Dradius-v.out17 Access-Challenge (11), id: 0x05, Authenticator: f050649184625d36f14c9075b7a48b83
/netbsd/src/external/bsd/ppp/dist/
DREADME.eap-srp1 EAP with MD5-Challenge and SRP-SHA1 support
12 This implementation includes the required default MD5-Challenge
98 For EAP MD5-Challenge, both client and server use the existing
DREADME.MSCHAP8012 Microsoft has introduced an extension to the Challenge/Handshake
DFAQ298 with CHAP (the Challenge Handshake Authentication Protocol). Both
360 CHAP stands for the Challenge Handshake Authentication Protocol. It
/netbsd/src/sys/arch/mips/
DREADME.models145 Challenge M ??
148 Challenge S (R4x00) R4?00 (MIPS-III) [portpage]
149 Challenge S (R5000) R5000 (MIPS-IV) [portpage]
/netbsd/src/crypto/external/bsd/libsaslc/dist/ref/
Drfc2195.txt14 IMAP/POP AUTHorize Extension for Simple Challenge/Response
78 2. Challenge-Response Authentication Mechanism (CRAM)
Drfc4422.txt361 S: Empty Challenge
421 S: Empty Challenge
Drfc2595.txt639 AUTHorize Extension for Simple Challenge/Response", RFC
Drfc2831.txt1114 AUTHorize Extension for Simple Challenge/Response", RFC
/netbsd/src/external/bsd/wpa/dist/wpa_supplicant/doc/docbook/
Dwpa_supplicant.sgml175 <para>EAP-PEAP/MD5-Challenge (both PEAPv0 and PEAPv1)</para>
179 <para>EAP-TTLS/EAP-MD5-Challenge</para>
215 <listitem><para>EAP-MD5-Challenge </para></listitem>
Dwpa_supplicant.conf.sgml102 <para>EAP-TTLS/EAP-MD5-Challenge configuration with anonymous
Dwpa_cli.sgml104 CTRL-REQ-OTP-2:Challenge 1235663 needed for SSID foobar
/netbsd/src/crypto/dist/ipsec-tools/src/racoon/rfc/
Ddraft-beaulieu-ike-xauth-02.txt296 5.2 Challenge/Response
353 Similar to the Challenge/Response method, this method allows
865 [CHAP] W. Simpson, "PPP Challenge Handshake Authentication Protocol
1207 RADIUS Chap Challenge
1217 Challenge = 0x01020304050607080910111213141516)
1223 where the Challenge in the REQUEST is the random number generated by
/netbsd/src/crypto/external/bsd/netpgp/dist/src/libpaa/
DPubKeyAccessAuthScheme.txt60 A.1 Challenge Generation
355 A.1 Challenge Generation
/netbsd/src/external/bsd/openldap/dist/doc/guide/
Dpreamble.sdf177 CRAM-MD5|SASL MD5 Challenge/Response Authentication Mechanism
/netbsd/src/crypto/external/bsd/heimdal/dist/doc/
Dinit-creds129 password"/"Enter it again", or "Challenge response"). The
/netbsd/src/share/misc/
Dacronyms.comp255 CHAP Challenge-Handshake Authentication Protocol

12