You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The docs state that the user should "Set up passwordless ssh to your server. Usually this means you have ssh-agent running with your private key loaded". Does it matter if ssh-agent is not used? It would be nice with an additional sentence along the lines of "This has only been tested by using ssh-agent for passwordless access", or "As long as you have passwordless access (i.e. you are not prompted for a password when running `ssh @<ip_adress>, you are good to go.", to inform users about what they should do and expect.
The text was updated successfully, but these errors were encountered:
You need passwordless access of some kind. Basically, running the ssh process to set up the tunnel shouldn't require any user input. I don't know whether there's options other than ssh-agent, so we could mention that.
We should probably just search for a good tutorial on how to set up ssh and link to that.
On the client, run ssh-keygen -t rsa. Accept default filename and location, and set no password.
On the server (RPi), create .ssh dir by mkdir -p .ssh
From the server, run ssh-copy-id pi@192.168.4.2 to upload key
It was somewhat different for non-linux client, but those instructions are also included. Could you verify that this tutorial looks good, and follows best practices? This is my first go as passwordless SSH, so I have no idea what the best practices are, if there are any.
The docs state that the user should "Set up passwordless ssh to your server. Usually this means you have ssh-agent running with your private key loaded". Does it matter if
ssh-agent
is not used? It would be nice with an additional sentence along the lines of "This has only been tested by usingssh-agent
for passwordless access", or "As long as you have passwordless access (i.e. you are not prompted for a password when running `ssh @<ip_adress>, you are good to go.", to inform users about what they should do and expect.The text was updated successfully, but these errors were encountered: