X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:reply-to:mime-version:to
	:subject:references:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=nTYECIsB9/Z1l6m/
	8eb9jogjelrMSnc9NGl8FT8r1aSTP6DJF6yAT1ZQaDllC4jii/9uf1VFRMlb6W1t
	iIUalIhvEbF786A7VtcIv1C8EDO/bGd6e6adoqz9e95MwQ+RyeJhR67ruc0oh8ML
	hpQqwT8esHUnB5bPDgN4cSuKYL4=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:reply-to:mime-version:to
	:subject:references:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=Vk3NQVztUcUDfHJE4mvwZY
	4b52k=; b=lihICBkhbYSYFWonfD9fcBmktRwA9RlpJclEgWvFa1NqW9zoUAQ/S3
	4pRi+rRwtiE62f50+h/BhB4Tk2g4lilO2VZ0vHF4hbYhS42+A72Ep+ab/cICjUmt
	XynUCxLmaHB33MPH1/hpGiGNmng1bYb9fkKgeO4DAgQ79RU3bJrVw=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.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
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=0.0 required=5.0 tests=AWL,BAYES_50,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2
X-HELO:	vms173017pub.verizon.net
X-CMAE-Score:	0
X-CMAE-Analysis:	v=2.1 cv=CoYIqc8G c=1 sm=1 tr=0 a=toTMxtHQF+05ooui8kuJQw==:117 a=vP6ySPhpAh4A:10 a=N659UExz7-8A:10 a=w_pzkKWiAAAA:8 a=oR5dmqMzAAAA:8 a=-9mUelKeXuEA:10 a=YNv0rlydsVwA:10 a=ez7ZyRnUukEAeeZmiKoA:9 a=pILNOxqGKmIA:10 a=As5FGbq2fYUA:10 a=JhvfxDshVtEA:10 a=TRvmKqLbH9UA:10
Message-id:	<54A77392.40704@cygwin.com>
Date:	Fri, 02 Jan 2015 23:44:02 -0500
From:	"Larry Hall (Cygwin)" <reply-to-list-only-lh AT cygwin DOT com>
Reply-to:	cygwin AT cygwin DOT com
User-Agent:	Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Thunderbird/31.3.0
MIME-version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: Never ending SSHD story: offering public key terminates connection
References:	<54A485DE DOT 1090802 AT nokia DOT com>
In-reply-to:	<54A485DE.1090802@nokia.com>

On 12/31/2014 06:25 PM, Ilya Dogolazky wrote:
> Hello !
>
> Using information posted provided by PolarStorm
> (https://www.cygwin.com/ml/cygwin/2014-12/msg00205.html) I managed to start
> the SSH daemon. As usual I started with a virgin virtual machine, installed
> Windows
> OS from DVD image, downloaded setup-x86_64.exe from cygwin.com, started it,
> added openssh package to the default set of packages, didn't change any
> package version. After the installer finished, I right clicked the terminal
> icon and started the Admin shell.  The transcript from this shell is
> attached as "log". The output of "cygcheck -s -v -r" is attached as well.
>
> The SSHD kinda works now, but not properly. Let's see what does it mean.
> First I tried to connect to my own cygwin host:
>
> ilya AT w9 ~ $ ssh localhost /bin/echo BLAH
> ilya AT localhost's password: [ *** typing my password here *** ]
> BLAH
> ilya AT w9 ~ $
>
> So... the connection, password authentication and remote execution work fine.
>
> Now I want to create a key pair first, and later try to use this pair to log
> in without typing my password. So let's create it:
>
> ilya AT w9 ~ $ ssh-keygen.exe

There may be nothing wrong with what you're doing here but using
ssh-user-config is the recommended and supported way of doing this.
You may want to check to be sure that the steps you're doing below
manually conform to the script that would do this for you automatically
and make the appropriate adjustments, if any.

<snip>

> The summary: a client offering a key is a reason enough for the server just
> to say goodbye and terminate the connection.  The file /var/log/sshd.log is
> present on my system, but it is empty. I tried to increase the log level in
> sshd_config file, but it doesn't work: the log file is always empty, so I
> don't have a clue what's happening on the server side.  Neither can I start
> the sshd manually with the '-d' flag, because of some permission error I
> don't understand.

Don't use 'ssh-host-config -y'.  Drop the flag and configure it manually so
that you get a proper password.

If you don't have a "root" in your '/etc/group' file, that suggests that
'/etc/postinstall/000-cygwin-post-install.sh' didn't run or didn't run
properly.  Try running it or the like-named file ending in ".done" taking
particular note of any output.  If your '/etc/group' file has the "root"
group now, you're good to go.  Try running 'ssh-host-config' again and see
if that helps.

If that doesn't work, you may have gotten caught by permissions settings as
a result of having the sshd service improperly started by the SYSTEM user.
You can either go through all those settings in the ssh-host-config script
and compare them with what you have or you could just wipe out your
installation and start over (OK, there are "in-between" possibilities too
that are less drastic but require more effort - I think you get the picture
;-) ).


-- 
Larry

_____________________________________________________________________

A: Yes.
 > Q: Are you sure?
 >> A: Because it reverses the logical flow of conversation.
 >>> Q: Why is top posting annoying in email?

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

- Raw text -