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=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: | Thu, 5 Apr 2012 12:33:19 +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: | <20120405103318.GA5442@pris.crapsteak.org> |
References: | <4F7C0884 DOT 2080006 AT gmail DOT com> <74924010 DOT 20120404152639 AT mtu-net DOT ru> <20120404133001 DOT GA8876 AT pris DOT crapsteak DOT org> <4F7D2B6D DOT 8070306 AT gmail DOT com> |
MIME-Version: | 1.0 |
In-Reply-To: | <4F7D2B6D.8070306@gmail.com> |
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 |
--mYCpIKhGyMATD0i+ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable (replying to the list, sorry if it breaks the thread) On Thu, Apr 05, 2012 at 03:19:41PM +1000, Rurik Christiansen wrote: > I was hoping more for some pointers to what the permissions must be and > then do the troubleshooting myself. > The "unix" side of permissions look ok. > I don't know what the windows side must be or if it matters. > The "ssh -vvv' (client side) has not been particularly helpful to me > when it comes to permissions. > and my understanding is that I can't run the sshd frontend without > screwing the permissions. > (the client sends the publickey packet and then jumps to next auth method) How did you setup the server? IIRC, ssh-host-config complains if it finds wrong perms. How do you start the service? Is there something in /var/log/sshd.log (provided you are logging there, and not elsewhere via syslog-ng or other means). You could also delete the service and recreate it. --=20 Primary key fingerprint: AD8F BDC0 5A2C FD5F A179 60E7 F79B AB04 5299 EC56 --mYCpIKhGyMATD0i+ Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iF4EAREIAAYFAk99dOoACgkQ95urBFKZ7FbKbAD+Ii5CyYo8U08P3BNkVZEBokl2 j+BUOQ79OASt+qUVvkIA/irdx5FL9RsxRiMqzZSTSkoJwjEhUEyKEzFP1TIQDQ21 =DITZ -----END PGP SIGNATURE----- --mYCpIKhGyMATD0i+--
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |