Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Mon, 19 Jan 2004 13:58:42 +0200
Message-Id: <200401191158.i0JBwg36008545@beta.mvs.co.il>
From: "Ehud Karni" <ehud AT unix DOT mvs DOT co DOT il>
To: marc DOT poppleton AT teamlog DOT com
Cc: cygwin AT cygwin DOT com, jurgen DOT defurne AT philips DOT com
Subject: Re: SSH key authentification problem
In-reply-to: <BKEALJICMGLKMNFJIFACOEBNCAAA.marc.poppleton@teamlog.com> (message from Marc Poppleton on Mon, 19 Jan 2004 12:06:54 +0100)
Organization: Mivtach-Simon Insurance agencies
Reply-to: ehud AT unix DOT mvs DOT co DOT il
References:  <BKEALJICMGLKMNFJIFACOEBNCAAA DOT marc DOT poppleton AT teamlog DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-8-i
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Mon, 19 Jan 2004 12:06:54 +0100, Marc Poppleton <marc DOT poppleton AT teamlog DOT com> wrote:
>
> > The problem's probably on the server end. It must be configured to
> > accept pubkey auth, as well as having your public key installed
> > properly.  You can see that the client tries pubkey but it's not
> > accepted.
>
> Yes, this is what it looks like to me.

The public key may be disallowed because of wrong permissions on the
server side. If you are logging into your own account on the server,
check that:
  Your home directory ($HOME) has no write permissions to group/other.
  Your SSH directory ($HOME/.ssh) is accessed only by you (i.e. 700)
  Your authorized keys file (authorized_keys or authorized_keys2) is
       in the SSH directory, not writable by others and has your
       public key in it.

If for any reason your home directory is writable by others (this is
a security breach), your system administrator can allow it by changing
the sshd configuration file (/etc/ssh/sshd_config) and restarting sshd.
She should check for the following line:
    StrictModes no             (default is yes)

Ehud.


- --
 Ehud Karni           Tel: +972-3-7966-561  /"\
 Mivtach - Simon      Fax: +972-3-7966-667  \ /  ASCII Ribbon Campaign
 Insurance agencies   (USA) voice mail and   X   Against   HTML   Mail
 http://www.mvs.co.il  FAX:  1-815-5509341  / \
 GnuPG: 98EA398D <http://www.keyserver.net/>    Better Safe Than Sorry
-----BEGIN PGP SIGNATURE-----
Comment: use http://www.keyserver.net/ to get my key (and others)

iD8DBQFAC8ZxLFvTvpjqOY0RAuLiAJ0Tw1SXdSWAzNMgBbZcfTBiRZ8JTQCcC9ba
lp4ecbT6WJV7Pyokqb6dvZo=
=g5d4
-----END PGP SIGNATURE-----

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/