Mail Archives: cygwin/2008/07/08/12:37:02
I am working on a windows 2000 box that openssh recently stopped working on.
For several months openssh worked correctly through cygwin as a service,
until the box was errantly shut down by a power outage. Subsequent attempts
to log in to said box through ssh resulted in authentication errors.
Several different attempts to solve the problem have since been attempted,
including the re-installation of openssh, followed by later the
re-installation of cygwin into a new directory. Now we are instead blessed
with the windows "error 1062" when trying to start openssh.
I have seen a variety of solutions for this problem (such as checking the
permissions on /var/empty, correcting /etc/passwd for the user 'sshd',
explicitly setting windows permissions for the cygwin directory to the user
SYSTEM, and verifying the windows registry keys). None of the proposed
solutions have made a difference.
I have also tried running it from the cygwin prompt as administrator (after
adjusting permissions on /var/empty accordingly). This does not work
correctly, either. If I run it this way, I am back to where I was before -
password authentication fails, even when connecting to localhost as a
non-administrator user who has a valid home directory and valid shell path.
I am out of ideas on this problem. My current installation of cygwin is in
a completely new directory - I moved my previous installation from
"C:\cygwin" to "C:\cygwin-old" and installed the new one as "C:\cygwin".
I'm not sure if this is important, but I noticed when I ran 'ssh-host-config
-y' as administrator, it never gave a "CYGWIN=" prompt. I haven't found a
good explanation for this behavior, either.
This is "OpenSSH_5.0p1, OpenSSL 0.9.8h May 2008" on cygwin from setup
2.573.2.2.
thank you
Lee Parsons
--
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/
- Raw text -