/freebsd/contrib/wpa/hostapd/ |
H A D | hlr_auc_gw.txt | 4 database/authentication gateway interface to HLR/AuC. It could be 6 authentication center (HLR/AuC). hostapd will send SIM/AKA 7 authentication queries over a UNIX domain socket to and external 10 hlr_auc_gw can be configured with GSM and UMTS authentication data with 13 dynamic authentication data for EAP-SIM, EAP-AKA, and EAP-AKA' while the 34 -g<triplet file> = path for GSM authentication triplets 79 authentication server for EAP-SIM/AKA/AKA':
|
H A D | README | 2 Authenticator and RADIUS authentication server 56 included in the kernel driver: using external RADIUS authentication 62 EAP server (i.e., allow full authentication without requiring 63 an external RADIUS authentication server), and RADIUS authentication 64 server for EAP authentication. 81 Any wired Ethernet driver for wired IEEE 802.1X authentication 104 minimal authentication mechanism for stations, whereas IEEE 802.1X 110 a station and it performs the authentication with the Authentication 149 will first perform IEEE 802.11 authentication. This is normally done 150 with open systems authentication, so there is no security. After [all …]
|
H A D | hostapd.eap_user | 7 # in unicode) if it is used for MSCHAP or MSCHAPv2 authentication. This means 13 # 2 authentication (e.g., within EAP-PEAP). In these cases, an anonymous 27 # avoid having to configure every certificate for EAP-TLS authentication. The 45 # EAP-TTLS supports both EAP and non-EAP authentication inside the tunnel.
|
H A D | ChangeLog | 113 - improved anti-clogging token mechanism and SAE authentication 149 - allow local VLAN management with remote RADIUS authentication 166 * added support for FILS (IEEE 802.11ai) shared key authentication 413 * enforce full EAP authentication after RADIUS Disconnect-Request by 445 - allow authentication log to be written into SQLite database 477 * added support for simultaneous authentication of equals (SAE) for 478 stronger password-based authentication with WPA2-Personal 553 * EAP-SIM: fixed re-authentication not to update pseudonym 779 authentication server 816 * fixed WEP authentication (both Open System and Shared Key) with [all …]
|
/freebsd/crypto/openssh/ |
H A D | sshd_config | 59 # Change to yes to enable built-in password authentication. 64 # Change to no to disable PAM authentication 77 # Set this to 'no' to disable PAM authentication, account processing, 78 # and session processing. If this is enabled, PAM authentication will 81 # PAM authentication via KbdInteractiveAuthentication may bypass 84 # PAM authentication, then enable this but set PasswordAuthentication
|
H A D | OVERVIEW | 76 implement X11 forwarding, TCP/IP forwarding, and authentication 82 - Code to communicate with the authentication agent is in authfd.c. 86 - Code for various authentication methods resides in auth-*.c 93 - In the client end, authentication code is in sshconnect.c. It 96 authentication agent using authfd.c. 103 proxy), and performs authentication (ssh_login in sshconnect.c). 139 negotiate encryption, then perform authentication, preparatory 149 - authentication
|
H A D | PROTOCOL.u2f | 6 U2F is an open standard for two-factor authentication hardware, widely 7 used for user authentication to websites. U2F tokens are ubiquitous, 17 of SSH authentication. They can be configured to require indication 27 in this case, but a HTTP origin for the case of web authentication, 43 authentication. From sshd's perspective, a security key constitutes a 44 single factor of authentication, even if protected by a PIN or biometric 45 authentication. To enable multi-factor authentication in ssh, please 200 format data in the pre-authentication attack surface. Therefore, the 226 interact with FIDO authentication tokens. This standard builds upon the
|
H A D | PROTOCOL.certkeys | 1 This document describes a simple public-key certificate authentication 7 The SSH protocol currently supports a simple public key authentication 12 managed, passwordless authentication and centrally certified host keys. 14 These protocol extensions build on the simple public key authentication 15 system already in SSH to allow certificate-based authentication. The 21 A sshd server may be configured to allow authentication via certified 58 algorithm names to add support for certificate authentication without 63 using the existing SSH "publickey" authentication method described 251 used for authentication. 255 for authentication. Addresses are
|
H A D | README.privsep | 8 Privilege separation is now mandatory. During the pre-authentication 34 On Cygwin, Tru64 Unix and OpenServer only the pre-authentication part 35 of privsep is supported. Post-authentication privsep is disabled
|
/freebsd/contrib/wpa/wpa_supplicant/doc/docbook/ |
H A D | eapol_test.sgml | 49 authentication client code from hostapd. In addition, it has 66 test suite for a RADIUS authentication server.</para> 75 <para>tries to complete EAP authentication based on the network 77 on the local host. A re-authentication is triggered to test fast 78 re-authentication. The configuration file uses the same format for 96 <listitem><para>IP address of the authentication server. The 110 <listitem><para>UDP port of the authentication server. The 117 <listitem><para>Shared secret with the authentication server. 184 <listitem><para>Save configuration after authentication.
|
H A D | wpa_cli.sgml | 40 <para>wpa_cli can show the current authentication status, selected 45 authentication information, like username and password, if these 48 authentication where the authentication is based on a 68 <title>Interactive authentication parameters request</title> 70 <para>When wpa_supplicant need authentication parameters, like 79 authentication server.</para> 92 card -based authentication.</para>
|
H A D | wpa_background.sgml | 45 authentication does not protect against bit flipping packet 53 keyed packet authentication mechanism (Michael MIC).</para> 56 either use an external authentication server (e.g., RADIUS) and 82 pre-authentication, and PMKSA caching).</para>
|
/freebsd/lib/libpam/pam.d/ |
H A D | README | 27 account: non-authentication based authorization, based on time, 30 password: update authentication tokens. 48 use_first_pass: try authentication using password from the 50 try_first_pass: first try authentication using password from
|
/freebsd/crypto/openssl/doc/man3/ |
H A D | SSL_CTX_set1_sigalgs.pod | 40 signature algorithms related to client authentication, otherwise they are 62 The client authentication signature algorithms set by a server are sent 63 in a certificate request message if client authentication is enabled, 66 Similarly client authentication signature algorithms set by a client are 67 used to determined the set of client authentication shared signature
|
H A D | SSL_CTX_dane_enable.pod | 9 - enable DANE TLS authentication of the remote TLS server in the local 34 peer authentication. 40 DANE authentication is implemented in the L<X509_verify_cert(3)> function, and 89 If no TLSA records are added successfully, DANE authentication is not enabled, 90 and authentication will be based on any configured traditional trust-anchors; 91 authentication success in this case does not mean that the peer was 175 negative value when DANE authentication failed or was not enabled, a 188 The calls below will perform DANE authentication and arrange to match either 259 * are unusable, so continue the handshake even if authentication fails. 276 * application protocol supports informing the server that authentication [all …]
|
H A D | HMAC.pod | 17 - HMAC message authentication code 56 HMAC is a MAC (message authentication code), i.e. a keyed hash 57 function used for message authentication, which is based on a hash 60 HMAC() computes the message authentication code of the I<data_len> bytes at 113 HMAC_Final() places the message authentication code in I<md>, which 128 HMAC() returns a pointer to the message authentication code or NULL if
|
H A D | SSL_check_chain.pod | 47 meaningful for client authentication. 50 for client authentication. 72 signature algorithm, supported curves and in the case of client authentication
|
/freebsd/tools/regression/iscsi/ |
H A D | ctl.conf | 7 discovery-auth-group no-authentication 11 auth-group no-authentication
|
/freebsd/crypto/openssl/demos/ |
H A D | README.txt | 29 gmac.c Demonstration of GMAC message authentication 30 poly1305.c Demonstration of Poly1305-AES message authentication 31 siphash.c Demonstration of SIPHASH message authentication
|
/freebsd/contrib/openpam/doc/man/ |
H A D | pam.man | 3 of common authentication-related operations and provides a framework 11 The user requesting authentication is called the applicant, while the 21 grouped into four facilities: authentication, account management, 61 There are two authentication primitives:
|
/freebsd/crypto/heimdal/etc/ |
H A D | services.append | 16 kerberos-iv 750/udp kdc # Kerberos authentication--udp 17 kerberos-iv 750/tcp kdc # Kerberos authentication--tcp
|
/freebsd/contrib/wpa/wpa_supplicant/ |
H A D | README | 55 - WPA with EAP (e.g., with RADIUS authentication server) ("WPA-Enterprise") 56 Following authentication methods are supported with an integrate IEEE 802.1X 83 authentication) 92 * pre-authentication 180 machines. However, there can be used as inner authentication 214 protection, and non-keyed authentication does not protect against bit 222 keyed packet authentication mechanism (Michael MIC). 225 an external authentication server (e.g., RADIUS) and EAP just like 250 messages in initial key handshake, pre-authentication, and PMKSA caching). 259 negotiation with a WPA Authenticator and EAP authentication with [all …]
|
H A D | eap_testing.txt | 2 IEEE 802.1X/EAPOL authentication 9 IEEE 802.1X authentication automatically without need for wireless 16 I'm more than willing to add new RADIUS authentication servers to make 21 In order for me to be able to use a new authentication server, the 134 client authentication followed by TNC inside the tunnel 158 - EAP-TTLS / EAP-TNC (partial support; no authentication sequence) 234 (Server rejects authentication without any reason in debug log. It 378 - sends tunneled EAP-Success with MPPE keys and expects the authentication to
|
/freebsd/crypto/openssl/test/ssl-tests/ |
H A D | 04-client_auth.cnf.in | 128 # Successful handshake with client authentication. 158 # Successful handshake with client authentication non-empty names 189 # Handshake with client authentication but without the root certificate.
|
/freebsd/contrib/ntp/sntp/ |
H A D | invoke-sntp.texi | 70 * sntp authentication:: authentication option (-a) 112 -a Num authentication Enable authentication with the key auth-keynumber 191 @node sntp authentication 192 @subsection authentication option (-a) 193 @cindex sntp-authentication 195 This is the ``enable authentication with the key @var{auth-keynumber}'' option. 197 Enable authentication using the key specified in this option's
|