From: Helmut Djurkin <helmut@oblig.at>
To: "alexander.lopata" <alexander.lopata@gmail.com>
Cc: linux-admin@vger.kernel.org
Subject: Re: SSH
Date: Sun, 13 Jul 2008 08:55:08 +0200 [thread overview]
Message-ID: <4879A6CC.3060505@oblig.at> (raw)
In-Reply-To: <48794903.3040309@tut.by>
$HOME/.ssh/ should not be accessible by others
try 'chmod go-rwx $HOME/.ssh -R'
alexander.lopata schrieb:
> It seems that sshd does not see authorized_keys file in my home folder.
> What I've done is put my openSSH public key in
> %h/.ssh/authorized_keys and configure my ssh client to use
> corresponding private key. But SSH still ask password. What can be
> wrong ?
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-admin" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2008-07-13 6:55 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-13 0:14 SSH alexander.lopata
2008-07-13 6:55 ` Helmut Djurkin [this message]
2008-07-13 7:02 ` SSH Chamith Kumarage
-- strict thread matches above, loose matches on Subject: below --
2004-07-14 15:26 ssh Piszcz, Justin Michael
2004-07-14 15:42 ` ssh Antony Stone
2004-07-14 15:57 ` ssh Koyama Mituru
2004-07-14 16:07 ` ssh Antony Stone
2004-07-14 14:15 ssh IT Clown
2004-07-14 14:25 ` ssh Koyama Mituru
2003-01-14 21:28 ssh Simpson, Doug
2003-01-15 12:09 ` ssh Zander
2003-01-15 18:44 ` ssh MAB
2003-01-14 19:59 ssh Simpson, Doug
2002-07-09 16:10 SSH Fabien.LIOU
2002-07-09 16:54 ` SSH David Jackson
2002-07-09 18:30 ` SSH Michael H. Warfield
2002-07-02 16:06 ssh Timothy Wood
2002-07-02 16:25 ` ssh Stephen Smalley
2002-06-24 12:23 ssh Daniel Sercaianu
2002-06-24 13:31 ` ssh Antony Stone
2002-06-24 13:47 ` ssh Maciej Soltysiak
2002-06-24 13:56 ` ssh Ramin Alidousti
1998-01-28 5:02 SSH Alex deVries
1998-01-28 9:54 ` SSH Alan Cox
1998-01-28 9:54 ` SSH Alan Cox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4879A6CC.3060505@oblig.at \
--to=helmut@oblig.at \
--cc=alexander.lopata@gmail.com \
--cc=linux-admin@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.