From ae0d43f1af9d07e471ad85ead339c5ee43571f9c Mon Sep 17 00:00:00 2001 From: simon Date: Thu, 6 May 2004 11:27:58 +0000 Subject: [PATCH] A user at ARM just found his home directory was _world_ writable, and this caused public key authentication to fail in spite of following our instructions to the letter. It can't hurt to s/g-w/go-w/ here, just in case! git-svn-id: svn://svn.tartarus.org/sgt/putty@4205 cda61777-01e9-0310-a592-d414129be87e --- doc/pubkey.but | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/doc/pubkey.but b/doc/pubkey.but index d7e32340..8b9a3f95 100644 --- a/doc/pubkey.but +++ b/doc/pubkey.but @@ -1,4 +1,4 @@ -\versionid $Id: pubkey.but,v 1.21 2003/01/16 15:43:18 jacob Exp $ +\versionid $Id: pubkey.but,v 1.22 2004/05/06 11:27:58 simon Exp $ \C{pubkey} Using public keys for SSH authentication @@ -419,10 +419,10 @@ that server. You may also need to ensure that your home directory, your \c{.ssh} directory, and any other files involved (such as \c{authorized_keys}, \c{authorized_keys2} or \c{authorization}) are -not group-writable. You can typically do this by using a command -such as +not group-writable or world-writable. You can typically do this by +using a command such as -\c chmod g-w $HOME $HOME/.ssh $HOME/.ssh/authorized_keys +\c chmod go-w $HOME $HOME/.ssh $HOME/.ssh/authorized_keys Your server should now be configured to accept authentication using your private key. Now you need to configure PuTTY to \e{attempt} -- 2.11.0