On Sun, Jan 10, 2010 at 5:26 PM, Thomas Nisbach <nisb...@cityweb.de> wrote:
> Here is my SOLUTION and what I additionally found: > Using LSA-package (running cyglsa-config script and reboot) is (the only?) > solution (Larry recommended, too)! > I read Corinna's message (also linked by CYGWIN User's Guide, > http://cygwin.com/ml/cygwin-developers/2006-11/msg00000.html). Here she > mentions that it is necessary to use LSA or a special user account like > sshd_server. Before updating to CYGWIN 1.7.1 I did not use LSA or a special > user account. Everything run fine since mid of 2006 and all CYGWIN updates in > between. I still do not understand what the difference in 1.7.1 is. Therefore > here my investigations: > <snip> > > What I found (without LSA configured): > Changing my login shell to /usr/bin/telnet made it possible to make some > tests. Telnet was started by sshd on my login host but it e.g. was not > possible to run local commands via "!" command (...could not load ws2_32, > Win32 error 126). Via Sysinternals process explorer I found a lot of > privileges missing on the forked sshd and telnet process. I guess the > privilege to modify the PATH is missing because PATH of the telnet process was > empty (resulting in the error message above?) > > Conclusion: Should there be a recommandation in the User's guid to use LSA > when updating to 1.7.1 and using services like SSH? > This worked for me. I configured LSA and ssh worked as it did in Cygwin 1.5. -Greg -- 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
