Searched refs:CHAP (Results 1 – 20 of 20) sorted by relevance
| /NextBSD/share/examples/ppp/ |
| HD | ppp.secret.sample | 6 # You must ``enable'' either PAP or CHAP in your ppp.conf file. 12 # This doesn't work for CHAP connections as ppp must have access 13 # to the unencrypted password for CHAP.
|
| HD | ppp.conf.sample | 43 # or by demanding PAP or CHAP authentication from the client. 87 # If you want to use PAP or CHAP instead of using a unix-style login 89 # should send PAP or CHAP. By default, we send whatever we're asked for. 130 set authkey "somepasswd" # This profile assumes you're using PAP or CHAP. 410 # that the peer uses CHAP or PAP with the "enable" keyword. Both CHAP and 412 # are enabled, CHAP is requested first. If the client doesn't agree, PAP 416 # don't need to enable CHAP or PAP, but the user that has logged
|
| /NextBSD/contrib/wpa/wpa_supplicant/ |
| HD | eap_testing.txt | 79 EAP-TTLS/CHAP + - +2 + + + + + + - + - 154 - EAP-TTLS / CHAP 176 - EAP-TTLS / CHAP (using FreeRADIUS as inner auth srv) 203 - EAP-TTLS / CHAP 225 - EAP-TTLS / CHAP 266 - EAP-TTLS / CHAP 295 - EAP-TTLS / CHAP 323 - EAP-TTLS / CHAP 348 - EAP-TTLS / CHAP
|
| HD | README | 72 * EAP-TTLS/CHAP
|
| HD | ChangeLog | 2065 EAP-TTLS/CHAP
|
| /NextBSD/contrib/wpa/hostapd/ |
| HD | hostapd.eap_user | 48 # TTLS-CHAP, TTLS-MSCHAP, TTLS-MSCHAPV2. TTLS-PAP and TTLS-CHAP require a 92 "ttls-user" TTLS-PAP,TTLS-CHAP,TTLS-MSCHAP,TTLS-MSCHAPV2 "password" [2]
|
| HD | eap_testing.txt | 42 EAP-TTLS/CHAP + - + - + +
|
| HD | ChangeLog | 632 enabled with new method names TTLS-PAP, TTLS-CHAP, TTLS-MSCHAP,
|
| /NextBSD/usr.sbin/ctld/ |
| HD | token.l | 55 chap { return CHAP; }
|
| HD | parse.y | 59 %token ALIAS AUTH_GROUP AUTH_TYPE BACKEND BLOCKSIZE CHAP CHAP_MUTUAL 255 auth_group_chap: CHAP STR STR 588 target_chap: CHAP STR STR
|
| /NextBSD/release/picobsd/floppy.tree/etc/ppp/ |
| HD | ppp.secret.sample | 6 # You must ``enable'' either PAP or CHAP in your ppp.conf file.
|
| /NextBSD/usr.sbin/bsdconfig/include/ |
| HD | network_device.hlp | 27 a PAP or CHAP login you will also need to know how to use the various 30 "modem capabilities database". If you choose a PAP or CHAP login you
|
| /NextBSD/sbin/iscontrol/ |
| HD | iscontrol.h | 104 CHAP enumerator
|
| HD | iscontrol.c | 72 {"CHAP", CHAP},
|
| HD | login.c | 349 case CHAP: in authenticate()
|
| /NextBSD/usr.sbin/ppp/ |
| HD | README.changes | 75 o Set encrypt is no longer necessary. Ppp will respond to M$CHAP 108 o Ppp now accepts M$CHAP (as well as normal CHAP) by default. If this
|
| /NextBSD/tools/regression/iscsi/ |
| HD | iscsi-test.sh | 229 AuthMethod = CHAP 265 AuthMethod = CHAP 288 …etname "$TARGET2" -p "$TARGETIP:3260" --op=update --name node.session.auth.authmethod --value=CHAP
|
| /NextBSD/crypto/heimdal/ |
| HD | NEWS | 266 operation in the KDC, currently supports: CHAP, MS-CHAP-V2, SASL
|
| /NextBSD/share/misc/ |
| HD | pci_vendors | 22302 23b1 DH895XCC Series CHAP Counter 25922 8c23 8 Series Chipset Family CHAP Counters 26119 9c23 8 Series CHAP Counters
|
| /NextBSD/crypto/heimdal/lib/wind/ |
| HD | UnicodeData.txt | 10263 A364;YI SYLLABLE CHAP;Lo;0;L;;;;;N;;;;;
|