If local users do not have sufficient permission, they can request that a system administrator of the remote host copy the files for them. Only a user with authenticated permission should be able to copy files to the server. The best approach for securely authenticating SSH sessions, however, is to create a public key pair for the local computer and copy the public key file to the remote SSH server. SSH can be used without a prior exchange of public key pairs, and those uses can be reasonably secure.

The advantage of using a CLI version of SSH is that commands are consistent across OSes, unlike with GUI versions that may implement commands using a variety of GUI techniques. This tutorial uses examples from OpenSSH in Windows PowerShell and in Linux Bash (Bourne Again Shell) command-line interfaces ( CLIs), but they also should apply to the macOS version of OpenSSH. However, modern OSes, including Windows 10 and later, Linux and macOS, include command-line versions of the OpenSSH implementation of SSH. For example, the PuTTYgen program is a GUI version of ssh-keygen for use with PuTTY, a GUI implementation of SSH for Windows. GUI versions of SSH usually include the same functionality as the command-line versions.

use multiple public keys for different functions on the same server.

use the same public key on multiple remote servers and.upload the public key to a remote server to enable automated and authenticated logins.This tutorial shows how to use the ssh-keygen command to create a new public key and how to use that key to do the following:

Kore keygen