From 6a5316a54c2e2a50c56bf471fc8855f2e309d329 Mon Sep 17 00:00:00 2001 From: ben Date: Thu, 10 Mar 2005 17:04:26 +0000 Subject: [PATCH] Make it clear that even when using SSH 2, you only need the SSH-2 pubkey format if you're actually using the SSH-2 protocol. git-svn-id: svn://svn.tartarus.org/sgt/putty@5483 cda61777-01e9-0310-a592-d414129be87e --- doc/pubkey.but | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/doc/pubkey.but b/doc/pubkey.but index 401be6e7..d80689c1 100644 --- a/doc/pubkey.but +++ b/doc/pubkey.but @@ -405,13 +405,13 @@ of OpenSSH 2 the file might be called \c{authorized_keys2}. (In modern versions the same \c{authorized_keys} file is used for both SSH-1 and SSH-2 keys.) -\b If your server is \cw{ssh.com}'s SSH 2 product, you need to save -a \e{public} key file from PuTTYgen (see \k{puttygen-savepub}), and -copy that into the \c{.ssh2} directory on the server. Then you -should go into that \c{.ssh2} directory, and edit (or create) a file -called \c{authorization}. In this file you should put a line like -\c{Key mykey.pub}, with \c{mykey.pub} replaced by the name of your -key file. +\b If your server is \cw{ssh.com}'s product and is using SSH-2, you +need to save a \e{public} key file from PuTTYgen (see +\k{puttygen-savepub}), and copy that into the \c{.ssh2} directory on +the server. Then you should go into that \c{.ssh2} directory, and edit +(or create) a file called \c{authorization}. In this file you should +put a line like \c{Key mykey.pub}, with \c{mykey.pub} replaced by the +name of your key file. \b For other SSH server software, you should refer to the manual for that server. -- 2.11.0