Your browser does not allow storing cookies. We recommend enabling them.
User Authentication with Public Keys in File
In the following instructions,
Server is the remote host running the Secure Shell server that you are trying to connect to. ServerUser is the username on Server that you are logging in as. Client is the host running the Secure Shell client. ClientUser is the username on Client that should be allowed to log in to Server as ServerUser. See Figure User public-key authentication.
Figure : User public-key authentication
The instructions assume that
ClientUser is allowed to log in to Server as ServerUser using some other authentication method (usually password). [ Contents] [ Index] [ Contact Information | Support | Feedback | SSH Home Page | SSH Products ]
Copyright © 2007 SSH Communications Security Corp.
This software is protected by international copyright laws. All rights reserved. Copyright Notice Reduce Secure Shell risk. Get to know the NIST 7966. The NISTIR 7966 guideline from the Computer Security Division of NIST is a direct call to action for organizations regardless of industry and is a mandate for the US Federal government. Download now ISACA Practitioner Guide for SSH With contributions from practitioners, specialists and SSH.COM experts, the ISACA “SSH: Practitioner Considerations” guide is vital best practice from the compliance and audit community. Download now What we recommend to read next: Regulatory compliance for cybersecurity? Privileged access management related information NEAREST SSH.COM OFFICE SSH Communications Security, Inc. 460 Totten Pond Road #460 Waltham, MA 02140 USA 781-247-2100 Contact us