| /netbsd/src/lib/libpam/modules/pam_group/ |
| D | pam_group.c | 62 static int authenticate(pam_handle_t *, struct passwd *, int);
130 if ((pam_err = authenticate(pamh, pwd, flags)) != PAM_SUCCESS) in pam_sm_authenticate()
152 authenticate(pam_handle_t *pamh, struct passwd *pwd, int flags) in authenticate() function
|
| /netbsd/src/crypto/dist/ipsec-tools/src/racoon/rfc/ |
| D | draft-ietf-ipsec-isakmp-hybrid-auth-05.txt | 54 X-Auth Exchange is used to authenticate the remote User. The use of
123 stages. The first stage is used to authenticate the Edge Device and
152 authenticate each other); and symmetric (both participants use the
183 to authenticate a User. Usually, a simple authentication protocol
192 authenticate the Edge Device and to establish an IKE SA. In the
194 described in [XAUTH] is used to authenticate the Client. Even though
203 The servers use public-key techniques to authenticate themselves to
205 authenticate herself (or send other identification information, such
232 order to authenticate the User. Upon the successful completion of the
288 stage is a Phase 1 Exchange used to authenticate the Edge Device. The
[all …]
|
| /netbsd/src/external/bsd/ppp/dist/ |
| D | PLUGINS | 113 that the peer could authenticate itself to us. If it returns 1, pppd
114 will ask the peer to authenticate itself. If it returns 0, pppd will
115 not ask the peer to authenticate itself (but if authentication is
162 that the peer could authenticate itself to us. If it returns 1, pppd
163 will ask the peer to authenticate itself. If it returns 0, pppd will
164 not ask the peer to authenticate itself (but if authentication is
177 will fail to authenticate.
204 the peer refuses to authenticate when it is requested to. If the
|
| D | FAQ | 81 to authenticate themselves to each other.
87 auth # require the peer to authenticate itself
238 its routing table), it will require all peers to authenticate
245 the peer to authenticate itself. The reason is that such machines
247 authenticate itself. In that case the peer can use any IP address as
256 1. If possible, arrange for the peer to authenticate itself, and
260 2. If the peer refuses to authenticate itself, and will always be
272 Pppd will then not ask the peer to authenticate itself. If you do
334 authenticate itself. So A would authenticate itself to B, and B would
335 also authenticate itself to A (possibly using a different
[all …]
|
| D | README.eap-tls | 150 If the peer doesn't ask us to authenticate or doesn't use eap
151 to authenticate us, disconnect.
172 as written above and then run pppd with the 'auth' option to authenticate
179 authenticate (and to use eap) and to disconnect if it doesn't.
|
| D | SETUP | 15 refuse to authenticate itself to you. Some ISPs require a username
27 noauth # don't require the ISP to authenticate itself
|
| /netbsd/src/external/bsd/wpa/dist/hostapd/ |
| D | hostapd.deny | 1 # List of MAC addresses that are not allowed to authenticate (IEEE 802.11)
|
| D | hostapd.accept | 1 # List of MAC addresses that are allowed to authenticate (IEEE 802.11)
|
| /netbsd/src/usr.sbin/ldpd/ |
| D | conffile.h | 49 int authenticate; /* RFC 2385 */ member
|
| D | conffile.c | 354 nei->authenticate = 1; in Gneighbour()
|
| /netbsd/src/external/bsd/openpam/dist/doc/man/ |
| D | pam.man | 7 In PAM parlance, the application that uses PAM to authenticate a user
15 The sequence of operations the server goes through to authenticate a
|
| /netbsd/src/etc/pam.d/ |
| D | su.in | 12 … sufficient pam_group.so no_warn group=rootauth root_only authenticate
|
| D | README | 25 auth: prompt for a password to authenticate that the user is
|
| /netbsd/src/external/bsd/openldap/dist/doc/guide/admin/ |
| D | sasl.sdf | 19 to authenticate the user to the {{TERM:LDAP}} directory server using
24 authorization feature, allowing them to authenticate themselves and
132 To use the GSSAPI mechanism to authenticate to the directory, the
569 LDAP entry. The users authenticate to the web server to establish
570 their identity, but the web server CGI cannot authenticate to the
591 become that DN, users must first authenticate as one of the persons
593 to the LDAP database. If people were allowed to authenticate
601 authenticate itself as its own authentication DN and then authorize
603 identities during one LDAP session, it will need to authenticate
|
| /netbsd/src/external/bsd/openldap/dist/servers/slapd/ |
| D | slapd.ldif | 58 # Allow anonymous users to authenticate
|
| /netbsd/src/crypto/external/bsd/heimdal/dist/doc/ |
| D | whatis.texi | 29 services can authenticate each other.
140 To authenticate @var{B}, @var{A} might request that @var{B} sends
|
| D | misc.texi | 31 should try to authenticate with kerberised telnet, and if that fails try
|
| /netbsd/src/crypto/external/bsd/libsaslc/dist/ref/ |
| D | rfc2222.txt | 177 agents such as proxy servers to authenticate using their own
260 exchange. This data would, for example, authenticate the server to
568 the src_name is authorized to authenticate as the authorization
649 the client is authorized to authenticate as the authorization
801 servers to authenticate using their own credentials, yet request
825 secure the connection, either service would authenticate the client,
|
| D | rfc2595.txt | 124 authenticate.
209 [SASL] EXTERNAL mechanism MAY be used to authenticate once TLS
306 [SASL] MAY be used to authenticate once TLS client
368 [SASL] EXTERNAL mechanism MAY be used to authenticate once TLS
437 message = [authorize-id] NUL authenticate-id NUL password
438 authenticate-id = 1*UTF8-SAFE ; MUST accept up to 255 octets
|
| /netbsd/src/crypto/external/bsd/netpgp/dist/src/libpaa/ |
| D | PubKeyAccessAuthScheme.txt | 79 Access Authentication scheme allows an HTTP server to authenticate clients using
275 Note that in principle a client could be asked to authenticate itself to
360 in order to authenticate clients without maintaining state for all such
|
| /netbsd/src/external/bsd/ntp/dist/html/hints/ |
| D | bsdi | 47 if you're going to authenticate.
|
| /netbsd/src/external/bsd/ntp/dist/ntpq/ |
| D | ntpq-opts.def | 272 .It Ic authenticate Op Cm yes Ns | Ns Cm no
275 does not authenticate requests unless
278 .Ic authenticate Cm yes
286 .Ic authenticate
347 used to authenticate configuration requests.
379 be echoed) which will be used to authenticate configuration
|
| /netbsd/src/external/bsd/openldap/dist/doc/drafts/ |
| D | draft-behera-ldap-password-policy-xx.txt | 181 kind of policy related to the password used to authenticate. Among
351 authenticate. The general focus of this policy is to minimize the
815 be used to authenticate. If this attribute is not present or if the
849 may not be used to authenticate after a specified number of
854 password may be used to authenticate when the number of failed bind
866 be used to authenticate due to too many failed bind attempts. If
868 cannot be used to authenticate until reset by a password
881 attempts after which the password may not be used to authenticate.
1082 authenticate. A 000001010000Z value means that the account has been
1350 authenticate with an expired password. The passwordExpired error
[all …]
|
| /netbsd/src/crypto/external/bsd/openssh/dist/ |
| D | README.lpk | 101 …If a user wants to authenticate to log in a server the sshd, will first look for authentication me…
105 …If a user want to authenticate to log in a server, the sshd will first look for auth method includ…
|
| D | PROTOCOL.chacha20poly1305 | 44 and authenticate the entire packet.
|