Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
From:	"Richard Stanton" <stanton AT Haas DOT Berkeley DOT EDU>
To:	"cygwin" <cygwin AT cygwin DOT com>
Subject:	New openSSH - error message
Date:	Tue, 15 May 2001 09:28:33 -0700
Message-ID:	<LNBBKMIKMNGEJNEJICPHAEFIFBAA.stanton@haas.berkeley.edu>
MIME-Version:	1.0
X-Priority:	3 (Normal)
X-MSMail-Priority:	Normal
X-Mailer:	Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance:	Normal
X-MimeOLE:	Produced By Microsoft MimeOLE V5.50.4133.2400
In-Reply-To:	<20010514130640.B28152@cygbert.vinschen.de>

I just upgraded to the latest openSSH, and installed sshd as a service using
cygrunsrv - that part went flawlessly; thanks for the new utility.

I tested it by running "ssh localhost". I logged on OK, but I notice that I
have the following two errors in my event log:

1) The description for Event ID ( 0 ) in Source ( sshd ) cannot be found.
The local computer may not have the necessary registry information or
message DLL files to display messages from a remote computer. The following
information is part of the event: sshd : Win32 Process Id = 0x434 : Cygwin
Process Id = 0x434 : DSA authentication refused for stanton: bad ownership
or modes for '/c/.ssh/authorized_keys2'..

2) The description for Event ID ( 0 ) in Source ( sshd ) cannot be found.
The local computer may not have the necessary registry information or
message DLL files to display messages from a remote computer. The following
information is part of the event: sshd : Win32 Process Id = 0x434 : Cygwin
Process Id = 0x434 : RSA authentication refused for stanton: bad ownership
or modes for '/c/.ssh/authorized_keys2'..

Does this matter? By the way, I generated the file /c/.ssh/authorized_keys2
using the most recent version of ssh_host_config prior to the current
version, and didn't get these messages with the last sshd.exe.

Deleting the file completely doesn't seem to cause any problems (and gets
rid of these error messages).

Richard Stanton



--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

- Raw text -