-
Notifications
You must be signed in to change notification settings - Fork 2.5k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Update doc to explictly mention using ed25519 in ssh keys
Signed-off-by: Hongyi Shen <[email protected]>
- Loading branch information
Showing
1 changed file
with
5 additions
and
5 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -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,15 +75,15 @@ 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`: | ||
|
||
``` | ||
podman-remote system connection list | ||
Name Identity URI | ||
myuser* id_rsa ssh://[email protected]/run/user/1000/podman/podman.sock | ||
myuser* id_ed25519 ssh://[email protected]/run/user/1000/podman/podman.sock | ||
``` | ||
|
||
Now we can test the connection with `podman info`: | ||
|