[ale] ssh over Cygwin

[Terry Bailey]

I have done that numerous times.  That is the way I have been starting and 
stopping the sshd daemon.  It automatically starts when the Cygwin window 
is opened.  I don't know how this works; I don't see in run any control 
files/directories (e.g., rc3 , rc2.d).  I am pretty sure the problem is 
within the Windows environment.  It looks as though the entries in 
/etc/passwd simply point to conditions set in the Windows environment.  For 
instance, user xxx cannot login using ssh or sftp over The Internet by just 
simply being in the Users group within Windows.  However, with in the 
Windows environment, you can simply add user xxx to the administrators 
group and then, bam, suddenly xxx can login using ssh/sftp over The 
Internet.  Note that mkpasswd  -l > /etc/passwd was not rerun.  I have 
looked in the Local Security Settings within Windows but have found nothing.

The sshd daemon does not act this way on my Fedora box.  A  user can login 
to the Fedora box without having some special status.

Man, this is my last hurdle and I have spent many days on it.  Thanks for 
being interested.  Please keep doing R&D.


At 10:05 PM 2/16/2007, you wrote:
>try this in a cygwin shell:
>
>net start sshd
>
>you should be able to see sshd as a service under windows after that.
>
>On 2/16/07, Terry Bailey <terry at bitlinx.com> wrote:
> >
> >
> >  /bin/bash is at the end of every user in /etc/passwd
> >
> >
> >
> >  At 10:56 AM 2/16/2007, you wrote:
> >
> > -vvv will give you the most verbose output for openssh client.
> >  it sounds like the user shell failed to be spawned. you do have /bin/bash
> > in /etc/passwd for the user right?
> >
> >  On 2/15/07, Terry Bailey <terry at bitlinx.com> wrote:
> >
> >
> >
> >  Hi,
> >
> >  I have sshd running great on Cygwin on Windows 2003, but only for
> > administrator.  I have two other users for R and D, xxx and yyy.  So 
> xxx and
> > yyy are not excepted over The Internet.  I changed xxx to be an
> > administrator in the Windows environment and now xxx works with ssh.  I did
> > an ssh ?v yyy at 126.23.43.23.  Everything went well through the password
> > (i.e., the password is accepted).  So the problem happens after getting
> > through the password phase.
> >
> >  The following is the extra output that I get with ssh ?v when I try to use
> > user yyy as opposed to using user xxx.
> >
> >
> >  debug1: client_input_channel_req: channel 0 rtype exit-status reply 0
> >  debug1: channel 0: free: client-session, nchannels 1
> >  Connection to 126.23.43.23 closed.
> >  debug1: Transferred: stdin 0, stdout 0, stderr 45 bytes in 0.6 seconds
> >  debug1: Bytes per second: stdin 0.0, stdout 0.0, stderr 77.5
> >  debug1: Exit status 128
> >  [root at dell ~]#
> >
> >  Any help would be appreciated.
> >
> >  Thanks,
> >
> >  Terry Bailey
> >
> >  _______________________________________________
> >  Ale mailing list
> >  Ale at ale.org
> >  http://www.ale.org/mailman/listinfo/ale
> >  _______________________________________________
> >  Ale mailing list
> >  Ale at ale.org
> >  http://www.ale.org/mailman/listinfo/ale
> > _______________________________________________
> > Ale mailing list
> > Ale at ale.org
> > http://www.ale.org/mailman/listinfo/ale
> >
>
>
>--
>Occam's eraser: The philosophical principle that even the simplest
>solution is bound to have something wrong with it.
>_______________________________________________
>Ale mailing list
>Ale at ale.org
>http://www.ale.org/mailman/listinfo/ale