nhyatt/putty-source
1
0
Fork 0
mirror of https://git.tartarus.org/simon/putty.git synced 2025-05-28 07:14:48 -05:00
Code Issues Projects Releases Wiki Activity

A user at ARM just found his home directory was _world_ writable,

Browse Source 
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]
This commit is contained in:
Simon Tatham 2004-05-06 11:27:58 +00:00
parent 10aca4e3ab
commit d18cd16ca1
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
doc/pubkey.but
View File

@ -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}