<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>SSHKeys &amp;mdash; Paul Sutton</title>
    <link>https://personaljournal.ca/paulsutton/tag:SSHKeys</link>
    <description>Personal Blog</description>
    <pubDate>Tue, 05 May 2026 15:00:49 +0000</pubDate>
    <item>
      <title>ssh - secure shell</title>
      <link>https://personaljournal.ca/paulsutton/ssh-secure-shell</link>
      <description>&lt;![CDATA[ssh - secure shell&#xA;&#xA;Secure shell is a remote login client.   The following is from the man page&#xA;&#xA;DESCRIPTION&#xA;       ssh (SSH client) is a program for logging into a remote machine and for executing  commands on a remote machine.  It is intended to provide secure encrypted communications between two untrusted hosts over an insecure network.  X11 connections, arbitrary  TCP  ports  and  Unix-domain sockets can also be forwarded over the secure channel.&#xA;So as mentioned before, vfsync can&#39;t do everything, so if you do need a full Linux system to log in to and install what you want.  By this, I am saying you also need to at least have sudo access to that remote system, even if this is a Raspberry Pi. &#xA; &#xA;While being able to log in with &#xA;&#xA;ssh user@host &#xA;Is useful, you still need a password,  which is fine.  If you want to use some services provided by [vern.cc] then you need to be able to log in with an authentication key.  This can be generated with&#xA;&#xA;ssh-keygen&#xA;DESCRIPTION&#xA;       ssh-keygen generates, manages  and  converts  authentication  keys  for  ssh(1).  ssh-keygen can create keys for use by SSH protocol version 2.&#xA;Which will generate a public / private key pair&#xA;&#xA;man ssh-copy-id &#xA;&#xA;NAME&#xA;       ssh-copy-id  —  use locally available keys to authorise logins on a re‐mote machine&#xA;&#xA;DESCRIPTION&#xA;       ssh-copy-id  is  a script that uses ssh(1) to log into a remote machine  (presumably using a login password, so password  authentication  should be enabled, unless you&#39;ve done some clever use of multiple identities).  It  assembles  a  list of one or more fingerprints (as described below) and tries to log in with each key, to see if any of  them  are  already installed (of course, if you are not using ssh-agent(1) this may result  in  you being repeatedly prompted for pass-phrases).  It then assembles a list of those that failed to log in and, using ssh(1), enables logins with those keys on the remote server.  By default it adds the  keys  by appending  them  to  the remote user&#39;s ~/.ssh/authorized_keys (creating  the file, and directory, if necessary).  It is also capable of  detecting if the remote system is a NetScreen, and using its ‘set ssh pka-dsa&#xA;       key ...’ command instead.&#xA;&#xA;There is some good information here too&#xA;&#xA;ssh cheat sheet&#xA;&#xA;The following allowed me to remote login to my Raspberry Pi  from my desktop&#xA;&#xA;cd .ssh (I did this so I was in the right place to generate the key)&#xA;ssh-keygen&#xA;ssh-copy-id -i ~/.ssh/Pi4.pub paul@xxx.xxx.xxx.xxx&#xA;ssh paul@xxx.xxx.xxx.xxx&#xA;Login with password, and you will be asked for the passphrase the first time you do this.  After which, you will be able to just ssh in without the password. &#xA;&#xA;Replace the x&#39;s with your IPv4 address. &#xA;&#xA;While using vern,  I had to use&#xA;ssh-keygen -lf ./key.pub&#xA;To address an error, it came up with about keyboard authentication.    This worked for me,  but should not &#39;just&#39; be used in every situation.&#xA;&#xA;Graphical ssh&#xA;&#xA;With Linux mint, it is also possible to connect the file manager nemo to a remote server.&#xA;&#xA;File -  Connect to server, then fill in the credentials.&#xA;&#xA;Remote with nemo&#xA;&#xA;With folder, it is probably a good idea to enter the path to your home directory on the remote server, so for a Raspberry Pi with a default username of pi, this is:-&#xA;&#xA;/home/pi&#xA;&#xA;Chat&#xA;&#xA;I am on the Devon and Cornwall Linux user group mailing list and also their matrix channel as zleap, it is better to ask there, that way others can answer too.&#xA;&#xA;Tags&#xA;&#xA;#Bash,#Linux,#ssh,#RemoteAccess,#Security,#SSHKeys,#SecureShell&#xA;&#xA;hr&#xD;&#xA;&#xD;&#xA;table&#xD;&#xA;thead&#xD;&#xA;trtda rel=&#34;me&#34; href=&#34;https://qoto.org/@zleap&#34;Mastodon/a/td&#xD;&#xA;tda href=&#34;https://wiki.ircnow.org/?n=Shelllabs.Intro&#34;ShellLabs/td&#xD;&#xA;tda href=&#34;https://joinmastodon.org/&#34;Join Mastodon/a/td/tr/thead/table&#xD;&#xA;center&#xD;&#xA;AI statement : b Consent is NOT granted to use the content of this blog for the purposes of AI training or similar activity.  Consent CANNOT be assumed, it has to be granted. /b&#xD;&#xA;/center&#xD;&#xA;&#xD;&#xA;a href=&#34;https://liberapay.com/PaulSutton/donate&#34;img alt=&#34;Donate using Liberapay&#34; src=&#34;https://liberapay.com/assets/widgets/donate.svg&#34;/a&#xD;&#xA;]]&gt;</description>
      <content:encoded><![CDATA[<p>ssh – secure shell</p>

<p>Secure shell is a remote login client.   The following is from the man page</p>

<pre><code>DESCRIPTION
       ssh (SSH client) is a program for logging into a remote machine and for executing  commands on a remote machine.  It is intended to provide secure encrypted communications between two untrusted hosts over an insecure network.  X11 connections, arbitrary  TCP  ports  and  Unix-domain sockets can also be forwarded over the secure channel.
</code></pre>

<p>So as mentioned before, <a href="https://personaljournal.ca/paulsutton/vfsync" rel="nofollow">vfsync</a> can&#39;t do everything, so if you do need a full Linux system to log in to and install what you want.  By this, I am saying you also need to at least have sudo access to that remote system, even if this is a Raspberry Pi.</p>

<p>While being able to log in with</p>

<pre><code>ssh user@host 
</code></pre>

<p>Is useful, you still need a password,  which is fine.  If you want to use some services provided by [vern.cc] then you need to be able to log in with an authentication key.  This can be generated with</p>

<pre><code>ssh-keygen
</code></pre>

<pre><code>DESCRIPTION
       ssh-keygen generates, manages  and  converts  authentication  keys  for  ssh(1).  ssh-keygen can create keys for use by SSH protocol version 2.
</code></pre>

<p>Which will generate a public / private key pair</p>

<pre><code>man ssh-copy-id 

NAME
       ssh-copy-id  —  use locally available keys to authorise logins on a re‐mote machine

DESCRIPTION
       ssh-copy-id  is  a script that uses ssh(1) to log into a remote machine  (presumably using a login password, so password  authentication  should be enabled, unless you&#39;ve done some clever use of multiple identities).  It  assembles  a  list of one or more fingerprints (as described below) and tries to log in with each key, to see if any of  them  are  already installed (of course, if you are not using ssh-agent(1) this may result  in  you being repeatedly prompted for pass-phrases).  It then assembles a list of those that failed to log in and, using ssh(1), enables logins with those keys on the remote server.  By default it adds the  keys  by appending  them  to  the remote user&#39;s ~/.ssh/authorized_keys (creating  the file, and directory, if necessary).  It is also capable of  detecting if the remote system is a NetScreen, and using its ‘set ssh pka-dsa
       key ...’ command instead.
</code></pre>

<p>There is some <a href="https://www.ssh.com/academy/ssh/copy-id" rel="nofollow">good information here too</a></p>
<ul><li><a href="https://www.sshhandbook.com/ssh-command-cheat-sheet/" rel="nofollow">ssh cheat sheet</a></li></ul>

<p>The following allowed me to remote login to my Raspberry Pi  from my desktop</p>

<pre><code>cd .ssh (I did this so I was in the right place to generate the key)
ssh-keygen
ssh-copy-id -i ~/.ssh/Pi4.pub paul@xxx.xxx.xxx.xxx
ssh paul@xxx.xxx.xxx.xxx
</code></pre>

<p>Login with password, and you will be asked for the passphrase the first time you do this.  After which, you will be able to just ssh in without the password.</p>

<p>Replace the x&#39;s with your IPv4 address.</p>

<p>While using vern,  I had to use</p>

<pre><code>ssh-keygen -lf ./key.pub
</code></pre>

<p>To address an error, it came up with about keyboard authentication.    This worked for me,  but should not &#39;just&#39; be used in every situation.</p>

<p>Graphical ssh</p>

<p>With Linux mint, it is also possible to connect the file manager nemo to a remote server.</p>

<p>File –&gt; Connect to server, then fill in the credentials.</p>

<p><img src="https://salsa.debian.org/zleap-guest/blog-media/-/raw/master/connecttoserver.png" alt="Remote with nemo"></p>

<p>With folder, it is probably a good idea to enter the path to your home directory on the remote server, so for a Raspberry Pi with a default username of pi, this is:-</p>

<pre><code>/home/pi
</code></pre>

<p><strong>Chat</strong></p>

<p>I am on the <a href="https://www.dcglug.org.uk/" rel="nofollow">Devon and Cornwall Linux user group</a> mailing list and also their <a href="https://matrix.to/#/%23dcglug:matrix.org" rel="nofollow">matrix channel</a> as zleap, it is better to ask there, that way others can answer too.</p>

<p><strong>Tags</strong></p>

<p><a href="/paulsutton/tag:Bash" class="hashtag" rel="nofollow"><span>#</span><span class="p-category">Bash</span></a>,<a href="/paulsutton/tag:Linux" class="hashtag" rel="nofollow"><span>#</span><span class="p-category">Linux</span></a>,<a href="/paulsutton/tag:ssh" class="hashtag" rel="nofollow"><span>#</span><span class="p-category">ssh</span></a>,<a href="/paulsutton/tag:RemoteAccess" class="hashtag" rel="nofollow"><span>#</span><span class="p-category">RemoteAccess</span></a>,<a href="/paulsutton/tag:Security" class="hashtag" rel="nofollow"><span>#</span><span class="p-category">Security</span></a>,<a href="/paulsutton/tag:SSHKeys" class="hashtag" rel="nofollow"><span>#</span><span class="p-category">SSHKeys</span></a>,<a href="/paulsutton/tag:SecureShell" class="hashtag" rel="nofollow"><span>#</span><span class="p-category">SecureShell</span></a></p>

<hr>

<p><table>
<thead>
<tr><td><a href="https://qoto.org/@zleap" rel="nofollow">Mastodon</a></td>
<td><a href="https://wiki.ircnow.org/?n=Shelllabs.Intro" rel="nofollow">ShellLabs</td>
<td><a href="https://joinmastodon.org/" rel="nofollow">Join Mastodon</a></td></tr></thead></table>

AI statement : <b> Consent is NOT granted to use the content of this blog for the purposes of AI training or similar activity.  Consent CANNOT be assumed, it has to be granted. </b>
</p>

<p><a href="https://liberapay.com/PaulSutton/donate" rel="nofollow"><img alt="Donate using Liberapay" src="https://liberapay.com/assets/widgets/donate.svg"></a></p>
]]></content:encoded>
      <guid>https://personaljournal.ca/paulsutton/ssh-secure-shell</guid>
      <pubDate>Tue, 20 May 2025 14:56:10 +0000</pubDate>
    </item>
  </channel>
</rss>