Differences between revisions 5 and 7 (spanning 2 versions)
Revision 5 as of 2021-11-18 16:50:57
Size: 1276
Comment:
Revision 7 as of 2023-01-09 02:07:33
Size: 1247
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
= SSH Keys = = SSH KeyGen =
Line 3: Line 3:
'''SSH Keys''' are used for password-less authentication. These carry a greater degree of security than password authentication, especially with careful control of your identity files. '''`ssh-keygen(1)`''' is used to generate public-private keypairs. These keypairs are used primarily by [[Encryption/OpenSSH|OpenSSH]].
Line 13: Line 13:
`ssh-keygen(1)` is bundled with `openssl`.

----



== Usage ==
Line 21: Line 29:
----
Line 23: Line 30:


== Usage ==

=== Server Configuration ===

SSH KeyGen

ssh-keygen(1) is used to generate public-private keypairs. These keypairs are used primarily by OpenSSH.


Installation

ssh-keygen(1) is bundled with openssl.


Usage

To generate a new SSH key, try:

ssh-keygen -t rsa -b 4096 -C "[email protected]"

Note that standards are always shifting. In the past, Github recommended a 2048 bits long key. Github now recommends the ed25519 algorithm, instead of rsa.

Legacy Format

OpenSSH 7.8+ uses a new format of SSH keys, which begin with -----BEGIN OPENSSH PRIVATE KEY-----. Some software are not prepared to parse this key format.

To generate a new key using the old format, add the -m PEM option.

To convert an existing key to the old format, try:

ssh-keygen -p -f ~/.ssh/id_rsa -m pem -P "" -N ""

Commercial Services

Github and Gitlab both allow SSH key authentication.


CategoryRicottone

Encryption/SSHKeyGen (last edited 2023-04-06 16:23:38 by DominicRicottone)