www.delorie.com/archives/browse.cgi | search |
X-Recipient: | archive-cygwin AT delorie DOT com |
X-SWARE-Spam-Status: | No, hits=-7.4 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,KHOP_PGP_SIGNED,KHOP_RCVD_TRUST,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE |
X-Spam-Check-By: | sourceware.org |
Date: | Wed, 4 Apr 2012 15:30:08 +0200 |
From: | David Sastre Medina <d DOT sastre DOT medina AT gmail DOT com> |
To: | cygwin AT cygwin DOT com |
Subject: | Re: sshd not doing key based authentication |
Message-ID: | <20120404133001.GA8876@pris.crapsteak.org> |
References: | <4F7C0884 DOT 2080006 AT gmail DOT com> <74924010 DOT 20120404152639 AT mtu-net DOT ru> |
MIME-Version: | 1.0 |
In-Reply-To: | <74924010.20120404152639@mtu-net.ru> |
User-Agent: | Mutt/1.5.21 (2010-09-15) |
X-IsSubscribed: | yes |
Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
List-Id: | <cygwin.cygwin.com> |
List-Unsubscribe: | <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com> |
List-Subscribe: | <mailto:cygwin-subscribe AT cygwin DOT com> |
List-Archive: | <http://sourceware.org/ml/cygwin/> |
List-Post: | <mailto:cygwin AT cygwin DOT com> |
List-Help: | <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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 |
--ikeVEW9yuYc//A+q Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Apr 04, 2012 at 03:26:39PM +0400, Andrey Repin wrote: > Greetings, Rurik Christiansen! > > I'm trying to make sshd to do key based authentication. > > I am guessing that is probably a problem of permissions but can't figure > > it out. > > All I found was this email: > > http://cygwin.com/ml/cygwin/2008-11/msg00212.html > > which basically says RTFM > > Well, I did RTFM, I followed the instructions. all looks OK as far as I > > can see but still no go. >=20 > Read logs on both sides, of course. > The most common issue is access rights on key files. Check for PubkeyAuthentication, StrictModes, AllowUsers, AllowGroups,=20 AuthorizedKeysFile in the server side (whether they exist and how they are= =20 defined), read the manpage for detailed info on this options (sshd_config(5)). Try setting LogLevel to DEBUG. Provide a 'ssh -vvv user AT host' test connection. You don't give enough info to figure out what the problem might be. --=20 Primary key fingerprint: AD8F BDC0 5A2C FD5F A179 60E7 F79B AB04 5299 EC56 --ikeVEW9yuYc//A+q Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iF4EAREIAAYFAk98TNUACgkQ95urBFKZ7FaW0AD+KGZc8yeYSuajvlpDU2ZDv5bR 6LswgNEAYxslTkdvrawA/0POcYw5EggpP2pX6p5Gq2db2/peq3VEeUP8Ndhnuc9J =Z32B -----END PGP SIGNATURE----- --ikeVEW9yuYc//A+q--
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |