diff options
| author | OpenShift Merge Robot <openshift-merge-robot@users.noreply.github.com> | 2021-12-02 20:02:48 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2021-12-02 20:02:48 +0100 |
| commit | 8bce756df9eb00c5b0b068cfebdbfc873a23a05c (patch) | |
| tree | 65a479cd8c0cdd0cb8a93e3f9063ffab7a0a6155 | |
| parent | b203e6d0f07d2c473c8249d0de173a2ca7176990 (diff) | |
| parent | babc693670b7558a955ea7827944ed82db15c6a4 (diff) | |
| download | podman-8bce756df9eb00c5b0b068cfebdbfc873a23a05c.tar.gz podman-8bce756df9eb00c5b0b068cfebdbfc873a23a05c.tar.bz2 podman-8bce756df9eb00c5b0b068cfebdbfc873a23a05c.zip | |
Merge pull request #12445 from wilbeibi/main
[CI:DOCS] Update doc to explictly mention using ed25519 in ssh keys
| -rw-r--r-- | docs/tutorials/remote_client.md | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/docs/tutorials/remote_client.md b/docs/tutorials/remote_client.md index 889947397..0370b0329 100644 --- a/docs/tutorials/remote_client.md +++ b/docs/tutorials/remote_client.md @@ -58,11 +58,11 @@ sudo systemctl enable --now -s sshd ``` #### Setting up SSH -Remote Podman uses SSH to communicate between the client and server. The remote client works considerably smoother using SSH keys. To set up your ssh connection, you need to generate an ssh key pair from your client machine. +Remote Podman uses SSH to communicate between the client and server. The remote client works considerably smoother using SSH keys. To set up your ssh connection, you need to generate an ssh key pair from your client machine. *NOTE:* in some instances, using a `rsa` key will cause connection issues, be sure to create an `ed25519` key. ``` -ssh-keygen +ssh-keygen -t ed25519 ``` -Your public key by default should be in your home directory under ~/.ssh/id_rsa.pub. You then need to copy the contents of id_rsa.pub and append it into ~/.ssh/authorized_keys on the Linux server. You can automate this using ssh-copy-id. +Your public key by default should be in your home directory under ~/.ssh/id_ed25519.pub. You then need to copy the contents of id_ed25519.pub and append it into ~/.ssh/authorized_keys on the Linux server. You can automate this using ssh-copy-id. If you do not wish to use SSH keys, you will be prompted with each Podman command for your login password. @@ -75,7 +75,7 @@ The first step in using the Podman remote client is to configure a connection. You can add a connection by using the `podman-remote system connection add` command. ``` -podman-remote system connection add myuser --identity ~/.ssh/id_rsa ssh://192.168.122.1/run/user/1000/podman/podman.sock +podman-remote system connection add myuser --identity ~/.ssh/id_ed25519 ssh://192.168.122.1/run/user/1000/podman/podman.sock ``` This will add a remote connection to Podman and if it is the first connection added, it will mark the connection as the default. You can observe your connections with `podman-remote system connection list`: @@ -83,7 +83,7 @@ This will add a remote connection to Podman and if it is the first connection ad ``` podman-remote system connection list Name Identity URI -myuser* id_rsa ssh://myuser@192.168.122.1/run/user/1000/podman/podman.sock +myuser* id_ed25519 ssh://myuser@192.168.122.1/run/user/1000/podman/podman.sock ``` Now we can test the connection with `podman info`: |