<story><title>Is your SSH password revealed when you attempt to connect to the wrong server?</title><url>http://unix.stackexchange.com/questions/309938/is-your-ssh-password-revealed-when-you-attempt-to-connect-to-the-wrong-server</url></story><parent_chain><item><author>userbinator</author><text>I find this common &amp;quot;wisdom&amp;quot; or &amp;quot;best practice&amp;quot; questionable. Something to think about:&lt;p&gt;If I use a password, a suitably designed client can have absolutely no trace of my credential after it has been used.&lt;p&gt;If I use a key&amp;#x2F;certificate, that credential must be stored &lt;i&gt;somewhere&lt;/i&gt; on the client, and even in encrypted form, it &lt;i&gt;exists&lt;/i&gt; in persistent storage.</text></item><item><author>alexk</author><text>I highly recommend to move off password-based SSH at all in favor of SSH keys or (even better, certificates).&lt;p&gt;Here are some projects to help you roll out new infrastructure without SSH passwords:&lt;p&gt;&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;gravitational&amp;#x2F;teleport&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;gravitational&amp;#x2F;teleport&lt;/a&gt; ( I work on this one with our team) and 
&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;Netflix&amp;#x2F;bless&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;Netflix&amp;#x2F;bless&lt;/a&gt; (heard great things about it, especially if you are using AWS)</text></item></parent_chain><comment><author>eli</author><text>If someone is able to steal my private key file, then they have probably compromised my computer and could just as well install a keylogger.</text></comment>
<story><title>Is your SSH password revealed when you attempt to connect to the wrong server?</title><url>http://unix.stackexchange.com/questions/309938/is-your-ssh-password-revealed-when-you-attempt-to-connect-to-the-wrong-server</url></story><parent_chain><item><author>userbinator</author><text>I find this common &amp;quot;wisdom&amp;quot; or &amp;quot;best practice&amp;quot; questionable. Something to think about:&lt;p&gt;If I use a password, a suitably designed client can have absolutely no trace of my credential after it has been used.&lt;p&gt;If I use a key&amp;#x2F;certificate, that credential must be stored &lt;i&gt;somewhere&lt;/i&gt; on the client, and even in encrypted form, it &lt;i&gt;exists&lt;/i&gt; in persistent storage.</text></item><item><author>alexk</author><text>I highly recommend to move off password-based SSH at all in favor of SSH keys or (even better, certificates).&lt;p&gt;Here are some projects to help you roll out new infrastructure without SSH passwords:&lt;p&gt;&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;gravitational&amp;#x2F;teleport&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;gravitational&amp;#x2F;teleport&lt;/a&gt; ( I work on this one with our team) and 
&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;Netflix&amp;#x2F;bless&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;Netflix&amp;#x2F;bless&lt;/a&gt; (heard great things about it, especially if you are using AWS)</text></item></parent_chain><comment><author>sfifs</author><text>Well you can always keep your keys in a removable drive rather than on persistent storage in your client device.&lt;p&gt;If you can&amp;#x27;t trust your client device, you probably have bigger issues with either method - for instance, can you trust that the client is not logging all keystrokes?</text></comment>