Michael Nelson wrote:
On Wed, May 09, 2007 at 01:30:35AM +0200, Joachim Schrod wrote:
Maybe because the file is named ~/.ssh/authorized_keys (with a "z"), i.e., American and not British spelling?
The other thing that tends to bite people is permissions on ~/.ssh/authorized_keys. It needs to be 644 ... ie: not writable by anyone but the owner. If the permissions are too loose, the passwordless login will fail.
You're right, another typical problem cause. And, home directory and ~/.ssh must not be world-writable either, and must be owned by the user; otherwise that blocks usage, too. (StrictModes parameter in sshd_config.) Joachim -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Joachim Schrod Email: jschrod@acm.org Roedermark, Germany -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wed, May 09, 2007 at 01:59:03AM +0200, Joachim Schrod wrote:
You're right, another typical problem cause. And, home directory and ~/.ssh must not be world-writable either, and must be owned by the user; otherwise that blocks usage, too. (StrictModes parameter in sshd_config.)
Speaking of sshd_config, if you really want to use the British spelling, you can set the "AuthorizedKeysFile" parameter to .ssh/authorised_keys. Michael -- In what was destined to be a short-lived spectacle, a chicken, suspended by a balloon, drifted through the Samurai bar's doorway. --Gary Larson San Francisco, CA -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (2)
-
Joachim Schrod -
Michael Nelson