{"id":132,"date":"2017-11-11T18:14:27","date_gmt":"2017-11-11T17:14:27","guid":{"rendered":"https:\/\/www.soft-toolware.net\/?p=132"},"modified":"2021-01-13T22:21:22","modified_gmt":"2021-01-13T21:21:22","slug":"ssh-public-key-authentication","status":"publish","type":"post","link":"https:\/\/www.soft-toolware.net\/?p=132","title":{"rendered":"ssh Public Key Authentication using ssh-keygen"},"content":{"rendered":"
\n
This post is based on differnet articles from www.ssh.com<\/a>.<\/span><\/h6>\n

The motivation for using public key authentication for ssh-Login over simple passwords is security. Public key authentication provides cryptographic strength that even extremely long passwords cannot.<\/span><\/p>\n

SSH Keys and Public Key Authentication<\/h5>\n

The SSH protocol uses public key cryptography for authenticating hosts and users. The authentication keys, called SSH keys, are created using the keygen<\/em> program. SSH introduced public key authentication as a more secure\u00a0 alternative to the older .rhosts<\/em> authentication.
\nIt improved security by avoiding the need to have password stored in files, and eliminated the possibility of a compromised server stealing the user’s
\npassword.<\/p>\n

However, SSH keys are authentication credentials just like passwords. Thus, they must be managed somewhat analogously to user names and passwords. They should have a proper termination process so that keys are removed when no longer needed.<\/p>\n

Key Pair – Public and Private<\/h5>\n

In the SSH public key authentication use case, it is rather typical that the users create (i.e. provision) the key pair for themselves. SSH implementations include easily usable utilities for this (for more information see ssh-keygen and ssh-copy-id).<\/p>\n

Each SSH key pair includes two keys:<\/p>\n