> From: Xavier Yin <wonderera2...@gmail.com>
> Hi, every one!
> I recently read Git on the Server - Setting Up the Server 
> <http://git-scm.com/book/en/Git-on-the-Server-Setting-Up-the-Server>, I 
> have a confusion about this paragraph as below:
> --------------------------------------------
> Key-based SSH authentication usually enforces security by requiring 
> restricted rights on the involved files. To prevent SSH from refusing to 
> work, type this:
> $ chmod -R go= ~/.ssh
> -----------------------

I don't know exactly what causes your issue, and I am not an expert in
SSH.  But I do know that the SSH server daemon enforces certain
restrictions on the permissions of the files in ~user/.ssh.  For
security it is important that no-one other than the user can read any
of the private key files.  Similarly, it is important that no-one
other than the user can modify any of the files in .ssh.  When a
client tries to authenticate as the user, the SSH daemon verifies that
the files in ~user/.ssh meet these requirements, and if they do not,
the daemon refuses the connection.  Probably the easiest way to ensure
that the .ssh directory meets these requirements is the chmod command
listed above.


You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to