Home
last modified time | relevance | path

Searched refs:authentication (Results 1 – 25 of 81) sorted by relevance

1234

/openbsd/src/lib/libssl/test/
Dtestssl38 echo test sslv2 with server authentication
42 echo test sslv2 with client authentication
45 echo test sslv2 with both client and server authentication
52 echo test sslv3 with server authentication
55 echo test sslv3 with client authentication
58 echo test sslv3 with both client and server authentication
64 echo test sslv2/sslv3 with server authentication
67 echo test sslv2/sslv3 with client authentication
70 echo test sslv2/sslv3 with both client and server authentication
76 echo test sslv2 with server authentication via BIO pair
[all …]
/openbsd/src/regress/lib/libssl/ssl/
Dtestssl23 echo test sslv2/sslv3 with server authentication
26 echo test sslv2/sslv3 with client authentication
29 echo test sslv2/sslv3 with both client and server authentication
43 echo test sslv2/sslv3 with server authentication
46 echo test sslv2/sslv3 with client authentication via BIO pair
49 echo test sslv2/sslv3 with both client and server authentication via BIO pair
52 echo test sslv2/sslv3 with both client and server authentication via BIO pair and app verify
121 echo test dtlsv1_2 with server authentication
124 echo test dtlsv1_2 with client authentication
127 echo test dtlsv1_2 with both client and server authentication
/openbsd/src/usr.bin/ssh/
DOVERVIEW76 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
DPROTOCOL.u2f6 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
DPROTOCOL.certkeys1 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
256 used for authentication.
260 for authentication. Addresses are
DPROTOCOL29 start of compression until after authentication has completed. This
43 authentication for users and host keys. These methods are documented
48 OpenSSH supports ECC key exchange and public key authentication as
167 1.11 transport: SSH2_MSG_EXT_INFO during user authentication
170 during user authentication. RFC8308 does allow a second
172 of user authentication and this is too late to signal per-user
176 authentication is signalled by the client including a
371 a client of all its protocol v.2 host keys after user-authentication
428 3.1. Host-bound public key authentication
430 This is trivial change to the traditional "publickey" authentication
[all …]
DPROTOCOL.agent29 should be bound for user authentication or forwarding.
34 previously bound for authentication. It will then record the
/openbsd/src/gnu/usr.bin/cvs/doc/
Dcvs.info-972 * :pserver:, setting up: Password authentication client.
95 * Authenticated client, using: Password authentication client.
96 * Authenticating server, setting up: Password authentication server.
143 * Client/Server Operation, port specification: Password authentication server.
177 * CVS passwd file: Password authentication server.
199 * CVS_PASSFILE, environment variable: Password authentication client.
299 * gserver (client/server connection method), port specification: Password authentication server.
347 * kserver (client/server connection method), port specification <1>: Password authentication server.
373 * Login (subcommand): Password authentication client.
375 * Logout (subcommand): Password authentication client.
[all …]
Dcvs.info-2220 (*note Password authentication client::).
347 Direct connection with password authentication
360 * Password authentication server:: Setting up the server
361 * Password authentication client:: Using the client
362 * Password authentication security:: What this method does and does not do
365 File: cvs.info, Node: Password authentication server, Next: Password authentication client, Up: …
367 Setting up the server for password authentication
372 authentication security::, for more details.
413 (almost--see *Note Password authentication security::, for details), a
419 an optional system username for CVS to run as if authentication
[all …]
Dcvsclient.info-198 * Security and authentication are handled outside this protocol (but
138 Connection and authentication occurs before the CVS protocol itself
155 authentication information, and then starts the cvs protocol.
164 authentication mechanisms, and a name for a specific mechanism
191 this authentication protocol and the cvs protocol, they are
195 The authentication is successful. The client proceeds with
199 The authentication fails. After sending this response, the
206 authentication protocol continues with another response.
213 The authentication fails. After sending this response, the
233 Another mechanism is GSSAPI authentication. GSSAPI is a generic
[all …]
Dcvs.aux82 'xrdef {Password authenticated-title}{Direct connection with password authentication}
85 'xrdef {Password authentication server-title}{Setting up the server for password authentication}
86 'xrdef {Password authentication server-pg}{21}
87 'xrdef {Password authentication server-snt}{Section'tie2.9.3.1}
88 'xrdef {Password authentication client-title}{Using the client with password authentication}
89 'xrdef {Password authentication client-pg}{23}
90 'xrdef {Password authentication client-snt}{Section'tie2.9.3.2}
91 'xrdef {Password authentication security-title}{Security considerations with password authenticatio…
92 'xrdef {Password authentication security-pg}{24}
93 'xrdef {Password authentication security-snt}{Section'tie2.9.3.3}
Dcvs.info67 Node: Password authentication server64757
68 Node: Password authentication client71729
69 Node: Password authentication security74928
DChangeLog43 * cvs.texinfo (Password authentication server, First import): Use
241 * cvs.texinfo (Password authentication server): Use -f in example
301 * cvs.texinfo (Password authentication server): The name of the
308 * cvs.texinfo (Password authentication server, Password
309 authentication client): Rewritten to accommodate the [new]
343 * cvs.texinfo (Password authentication server): Note inetd limits
387 * cvs.texinfo (Password authentication security): Remove sentence
421 protocol. Likewise for "E" and "error" in authentication protocol.
567 (Password authentication server): Remove comment about
650 * cvs.texinfo (Password authentication server): Say explicitly
[all …]
/openbsd/src/sbin/isakmpd/
DTO-DO49 * RSA signature authentication. <Niels> [done]
51 * DSS signature authentication.
53 * RSA encryption authentication.
Dipsec_num.cst71 # IPSEC authentication algorithm.
142 # IKE authentication method.
/openbsd/src/etc/ppp/
Dchap-secrets3 # Secrets for authentication using CHAP
Dpap-secrets3 # Secrets for authentication using PAP
/openbsd/src/regress/usr.sbin/ospfd/
DPacket.pm192 $$fields{authentication} = "" if $$fields{autype} == 0;
203 $packet .= pack("a8", $$fields{authentication});
/openbsd/src/regress/sbin/ipsecctl/
Dsafail1.ok2 stdin: 6: no encryption or authentication with ipcomp
/openbsd/src/share/snmp/
DSNMP-USER-BASED-SM-MIB.txt389 If the new user is to use authentication:
402 If the new user will never use authentication:
502 authentication parameters of the new user must be
504 - authentication protocol (usmUserAuthProtocol)
510 authentication key (authKey) and the secret encryption
539 the type of authentication protocol which is used.
583 authentication key used for messages sent on behalf
590 authentication key (authKey). The associated hash
655 his own secret authentication key (authKey).
702 must also use an authentication protocol. In other
[all …]
/openbsd/src/usr.sbin/npppd/npppd/
Dnpppd.conf4 authentication LOCAL type local {
/openbsd/src/etc/
Dservices66 auth 113/tcp authentication tap ident
191 radius 1812/udp # radius authentication
264 afs3-kaserver 7004/tcp # AFS kerberos authentication server
265 afs3-kaserver 7004/udp # AFS kerberos authentication server
299 kerberos-iv 750/udp kdc # Kerberos authentication--udp
300 kerberos-iv 750/tcp kdc # Kerberos authentication--tcp
/openbsd/src/regress/usr.sbin/bgpd/config/
Dbgpd.conf.17.in2 # Test various authentication statements
/openbsd/src/gnu/llvm/llvm/docs/
DPointerAuth.md19 [Armv8.3-A PAuth/Pointer Authentication Code](#armv8-3-a-pauth-pointer-authentication-code)
29 These intrinsics are provided by LLVM to expose pointer authentication
234 memory, negating the security benefit provided by pointer authentication.
268 authentication primitives, based on Armv8.3-A instructions.
/openbsd/src/regress/usr.bin/ssh/
Dintegrity.sh55 Corrupted?MAC* | *message?authentication?code?incorrect*)

1234