From: Simon Tatham <anakin@pobox.com>
Date: Thu, 6 May 2004 11:27:58 +0000 (+0000)
Subject: A user at ARM just found his home directory was _world_ writable,
X-Git-Tag: 0.55~41
X-Git-Url: https://asedeno.scripts.mit.edu/gitweb/?a=commitdiff_plain;h=d18cd16ca1979e6b14d61baa6aaf701d46d1e0f5;p=PuTTY.git

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!

[originally from svn r4205]
---

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}