569
edits
Changes
SSH RSA key authentication (Linux) (view source)
Revision as of 12:10, 14 April 2022
, 12:10, 14 April 2022Added -i option if commands to clarify the process
To achieve the configuration described in this article you will need the following:
To achieve the configuration described in this article you will need the following:
*A computer running on Linux
* A computer running on Linux
*A RUTxxx router of any type
* A RUTxxx router of any type
==Configuration==
==Configuration==
<pre>
<pre>
ssh-keygen
ssh-keygen
</pre>
</pre>When prompted, enter the file name, for example '''rsa_key'''. Two file will then be generated: '''rsa_key''' (private) and '''rsa_key.pub''' (public).
</li>
</li>
----
----
Next, we'll have to add the key to your RUTxxx router. Simply execute this command via a Terminal (replace the IP address with your router's IP):
Next, we'll have to add the key to your RUTxxx router. Simply execute this command via a Terminal (replace the IP address with your router's IP):
<pre>
<pre>
ssh-copy-id [email protected]
ssh-copy-id -i rsa_key.pub [email protected]
</pre>
</pre>
</li>
</li>
----
----
<li>'''NOTE: You only need to do this step once.''' The key will be added to the ''/root/.ssh/authorized_keys'' file. You must then move it to ''/etc/dropbear/'', and make a symlink from dropbear. To do so, login to the router via SSH and execute these commands:
<li>
The key will be added to the ''/root/.ssh/authorized_keys'' file. You must then copy it to ''/etc/dropbear/''. To do so, login to the router via SSH and execute this command:
<pre>
<pre>
cp /root/.ssh/authorized_keys /etc/dropbear/
</pre>
</pre>
</li>
</li>
----
----
<li>
<li>
Next, while still connected to the router, add ''read'', ''write'' and ''execute'' permissions for the ''/etc/dropbear'' directory and ''read'', ''write'' permissions for the ''/etc/dropbear/authorized_keys'' file:
<pre>
chmod 700 /etc/dropbear
chmod 600 /etc/dropbear/authorized_keys
</pre>
</li>
</li>
----
<li>
At this point, the configuration is complete. To test it, terminate your current SSH connection (you can do so by executing the ''exit'' command) and try logging in again - if everything is in order, the router should no longer require a password when connecting via SSH when using the command:<pre>
ssh -i rsa_key [email protected]
</pre></li>
----
----
<li>
<li>
==See also==
==See also==
*[[SSH RSA key authentication (Windows)]] - the same guide but aimed at Windows users
* [[SSH RSA key authentication (Windows)]] - the same guide but aimed at Windows users
*[[Command line interfaces]] - descriptions and instruction for all types of command line interfaces supported by RUTxxx devices
* [[Command line interfaces]] - descriptions and instruction for all types of command line interfaces supported by RUTxxx devices
