From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18232 invoked by alias); 13 May 2008 16:03:46 -0000 Received: (qmail 18219 invoked by uid 22791); 13 May 2008 16:03:44 -0000 X-Spam-Check-By: sourceware.org Received: from mail2.flooddata.com (HELO mail2.flooddata.com) (67.96.169.25) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 13 May 2008 16:03:15 +0000 Received: from localhost (localhost [127.0.0.1]) by mail2.flooddata.com (Postfix) with ESMTP id E403727EDA for ; Tue, 13 May 2008 11:03:12 -0500 (CDT) Received: from mail2.flooddata.com ([127.0.0.1]) by localhost (mail2.flooddata.com [127.0.0.1]) (amavisd-maia, port 10024) with ESMTP id 30781-05 for ; Tue, 13 May 2008 11:03:09 -0500 (CDT) Received: from callisto.flooddata.com (callisto.flooddata.com [10.5.0.33]) by mail2.flooddata.com (Postfix) with ESMTP id AB7A3475C8F for ; Tue, 13 May 2008 11:03:09 -0500 (CDT) Received: from fdsvast06sxch01.flooddata.net (athena.flooddata.com [10.3.1.61]) by callisto.flooddata.com (Postfix) with ESMTP id 9FF7CB52F for ; Tue, 13 May 2008 11:03:09 -0500 (CDT) Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: Unable to run sshd under a domain sshd_server account [SOLVED] Date: Tue, 13 May 2008 16:09:00 -0000 Message-ID: <3B3EFBD49B94AD4DBB7B7097257A8046DD02F7@FDSVAST06SXCH01.flooddata.net> In-Reply-To: References: <3B3EFBD49B94AD4DBB7B7097257A8046DD020D@FDSVAST06SXCH01.flooddata.net> <3B3EFBD49B94AD4DBB7B7097257A8046DD0232@FDSVAST06SXCH01.flooddata.net> From: "Schutter, Thomas A." To: X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com X-SW-Source: 2008-05/txt/msg00234.txt.bz2 > > > > > The application event log has this error message: > > > > > 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. You may be able to use the /AUXSOURCE=3D flag to > retrieve > > > > > this description; see Help and Support for details. The > following > > > > > information is part of the event: sshd: PID 2068: service > `sshd' > > > > > failed: signal 11 raised. > > > > > > Oops -- a segfault. This is definitely a bug somewhere -- no > matter > > > what, sshd should not segfault. > > > > Agreed. >=20 > Those problems are usually very hard to reproduce. If you're set up to > build a debug version of sshd and run it under gdb to reproduce the > fault, > a stack backtrace would be helpful. Unfortunately I am not setup to build a debug version. But I have tested on a new machine and can report that it happens if user running the sshd service does not have write permission to the /var/log/sshd.log file. In this case it actually seems easy to reproduce. > > > > In the other thread, Larry Hall pointed me to the FAQ > > > > http://cygwin.com/faq/faq-nochunks.html#faq.using.shares. One of > the > > > > suggestions was to "provide your password to a net use command". > I > > > > was unable to make that work, because "net use" never asks for my > > > > password: > > > > $ net use \\other\f$ > > > > System error 67 has occurred. > > > > > > > > The network name cannot be found. > > > > > > See "net help use": > > > The syntax of this command is: > > > NET USE > > > [devicename | *] [\\computername\sharename[\volume] [password | > *]] > > > ... > > > password Is the password needed to access the shared > > > resource. > > > * Produces a prompt for the password. The password > is > > > not displayed when you type it at the password > > > prompt. > > > > > > So, you need to type "net use '\\other\f$' \*" (note the > > escaped/quoted > > > '*'), and it'll prompt you for the password. > > > > OK. So on a console cygwin shell: > > $ net use '\\other\f$' > > The command completed successfully. > > > > But when run in a ssh shell (using the sshd_server account): > > $ net use '\\other\f$' \* > > Type the password for \\zoom\f$: System error 1326 has occurred. > > > > Logon failure: unknown user name or bad password. >=20 > Umm, yes. Sorry. I forgot that sshd runs in a pty, which is a pipe as > far as Windows is concerned. And 'net' cannot read the password from a > pipe... >=20 > > Same thing happens with: > > $ net use '\\other\f$' '*' > > $ net use '\\other\f$' "*" >=20 > Actually supplying the password instead of '*' should work. > Igor OK. The pipe thing makes sense. But supplying the password does not work either: $ net use '\\other\f$' MyPassword1 System error 1909 has occurred. The referenced account is currently locked out and may not be logged on to. -- Tom Schutter First American - Proxix Solutions (512) 977-6822 -- 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/