delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2001/03/30/01:07:10

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
Message-ID: <3AC43057.9010500@bigpond.com>
Date: Fri, 30 Mar 2001 17:05:59 +1000
From: Brendan J Simon <brendan DOT simon AT bigpond DOT com>
Reply-To: brendan DOT simon AT bigpond DOT com
User-Agent: Mozilla/5.0 (X11; U; Linux 2.4.2-bjs ppc; en-US; m18) Gecko/20001110
X-Accept-Language: en
MIME-Version: 1.0
To: cygwin AT sourceware DOT cygnus DOT com
Subject: Re: cygwin: can't get openssh working via inetd
References: <F59TkUD5euwdUTaGmvS00003866 AT hotmail DOT com>

Thanks Karl,

The new cygwin1.dll fixed the ssh problem I was seeing.  I can now login 
in successfully but I have to enter my password everytime.  Obviously 
the sshd is not looking into my home directory (which is on a mapped 
network drive) for my .ssh/ directory.  How do I get around this ???

Thanks,
Brendan Simon.



Karl M wrote:

> Hi Brendan...
> 
> I had the same problem. I downloaded the 20010325 snapshot of the 
> cygwin1.dll file and that took care of it. The issue shows up when the 
> user-id of the sshd is different than the user-id of the client.
> 
> ...Karl
> 
> 
>> From: Brendan J Simon <brendan DOT simon AT bigpond DOT com>
>> Reply-To: brendan DOT simon AT bigpond DOT com
>> To: cygwin <cygwin AT sourceware DOT cygnus DOT com>
>> Subject: cygwin: can't get openssh working via inetd
>> Date: Fri, 30 Mar 2001 12:03:18 +1000
>> 
>> I can't get sshd workding via inetd.  I'm following the instructions in
>> /usr/doc/Cygwin/openssh-2.5.1pw.README.
>> I it does work perfectly if I invoke sshd manually from the bash
>> prompt.  This indicates to me that there is a problem with sshd running
>> as SYSTEM and trying to fork and change users.  I see
>> 
>> [bjsimon AT k9:~]$ ssh zigfried
>> bjsimon AT zigfried DOT ctam DOT local's password:
>>    0 [main] a 0 handle_exceptions: Exception: STATUS_ACCESS_VIOLATION
>> Exception: STATUS_ACCESS_VIOLATION at eip=61001B47
>> eax=00000069 ebx=6779632F ecx=00000000 edx=67796337 esi=00000000
>> edi=0240FF74
>> ebp=0240FA30 esp=0240FECC program=a
>> cs=001B ds=0023 es=0023 fs=0038 gs=0000 ss=0023
>> Stack trace:
>> Frame     Function  Args
>> 0240FA30  61001B47  (00000000, 00000000, 00000000, 00000000)
>> 0240FEF4  61001B47  (00000130, 7FFD0001, 0240FF44, 6100326E)
>> 0240FF44  61003380  (004072CC, 6107D13C, 00000000, 00000000)
>> 0240FF74  61003A3D  (00000000, 00000000, 00000000, 00000000)
>> 0240FF94  61003A7C  (00407230, 004011D0, 0240FFC0, 00401038)
>> 0240FFA4  00405206  (004011D0, 80430F7B, 77E992A3, FFFFFFFE)
>> 0240FFC0  00401038  (00000000, 00000000, 7FFDF000, 0247D711)
>> 0240FFF0  77E992A6  (00401000, 00000000, 000000C8, 00000100)
>> End of stack trace
>> 
>> 
>> Is this an NTSEC problem ??  I'm running Windows 2000.
>> My /etc/ssh_config has everything commented out so it should have the
>> defaults.
>>   PasswordAuthentication yes
>>   RSAAuthentication yes
>> 
>> There is mention in the docs that when using ntea or ntsec you now have
>> to care for the ownership and permissions bits of your host key files
>> and your private key files.  I have tried changing the permissions and
>> ownership with chmod but nothing happens !!!  ie. chmod and chown don't
>> seem to have any affect.  I created a file in /tmp and tried to change
>> its owner to SYSTEM but ls -l reveals nothing changed.  The same when
>> trying chmod +w /tmp/file.
>> 
>> Why can't I change permissions and would this be the reason sshd running
>> as LocalSystem doesnot operate properly.
> 



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

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019