Lines Matching refs:authentication
7 from one machine to another. It provides strong authentication and
20 o Strong authentication. Closes several security holes (e.g., IP,
21 routing, and DNS spoofing). New authentication methods: .rhosts
22 together with RSA based host authentication, and pure RSA
23 authentication.
29 authentication, and no passwords or other information is
46 authentication if administration installs host key files.
50 authentication never trusts anything but the private key.
56 /etc/hosts.equiv authentication (to prevent DNS, routing, or
59 o Host authentication key distribution can be centrally by the
62 recorded and used for authentication in the future), or manually
66 is installed. Host authentication keys are typically 1024 bits.
68 o Any user can create any number of user authentication RSA keys for
71 key is accepted as authentication. User authentication keys are
84 o An authentication agent, running in the user's laptop or local
85 workstation, can be used to hold the user's RSA authentication
87 authentication agent over any connections, and there is no need to
88 store the RSA authentication keys on any machine in the network
89 (except the user's own local machine). The authentication
92 could rely on a smart card to perform all authentication
248 authentication and starts serving the client.
257 authentication keys).
260 keys for authentication.
277 authentication). The latter form executes the command on the remote
283 listener from getting the keys), performs authentication using .rhosts
284 and /etc/hosts.equiv, RSA authentication, or conventional password
285 based authentication. The server then (normally) allocates a
314 If there is an authentication agent on the client side, connection to
341 authentication data for the fake data (if the fake data matched), and
346 as the display. No authentication information is forwarded in this
350 machine. Using authentication data is always recommended because not
352 generates the authentication data.
376 RSA authentication is based on public key cryptograpy. The idea is
384 RSA authentication is based on the impossibility of deriving the
389 server the public key that the user wishes to use for authentication.
409 RSA authentication is the most secure form of authentication supported
429 Conventional .rhosts and hosts.equiv based authentication mechanisms
431 routing spoofing attacks. Additionally this authentication method
435 Ssh provides an improved version of these types of authentication,
438 authentication, but additionally requires that the client host be
451 attackers. If maximal security is desired, only RSA authentication
455 authentication (without host authentication) at compile time by giving
475 send his/her own requests to your authentication agent.