[ANNOUNCEMENT] Updated: OpenSSH-2.3.0p1-1
Wed Jan 10 10:37:00 GMT 2001
Interestingly, on my laptop, I did a new install (it had previously
exhibited the crash behavior).
Machine: Windows 2000 Pro running on Dell Latitude CSx.
Logging in as DOMAIN\erdelym. User has Local Administrator rights.
1. Deleted "Cygnus Solutions" registry keys.
2. Stopped and removed any Cygwin related services (SSHD & INETD).
3. Renamed C:\Cygwin -> C:\Cygwin.old
4. Downloaded and installed fresh, clean Cygwin from franken.de including
5. Deleted my local "erdelym" user from /etc/passwd.
6. Added my domain "erdelym" user to /etc/passwd including
7. Ran "iu-config".
8. Ran "ssh-config".
9. Copied /usr/sbin/sshd.exe /usr/sbin/in.sshd.exe.
10. Commented all services in /etc/inetd.conf out.
11. Added "sshd stream tcp nowait root /usr/sbin/in.sshd
sshd -i -d -d -d" to /etc/inetd.conf
12. Changed RSAAuth to no and PasswordAuth to yes in /etc/sshd_config.
12. Ran "chown system.system /etc/ssh_host*_key".
13. Ran "/usr/sbin/inetd --install-as-service".
14. Ran "net start inetd".
15. Ran "ssh -v -v -v localhost".
Success!!! No Dr. Watson errors. No stack trace dumps.
16. Ran "net stop inetd".
17. Removed "-d -d -d" from the sshd line in /etc/inetd.conf
18. Ran "net start inetd"
19. Ran ssh localhost.
20. Ran SecureCRT and connected to localhost.
Here are some of the things I _didn't_ do this time:
1. I normally customize PS1 in /etc/profile which involves using the output
of hostname | tr '[A-Z]' '[a-z]'.
2. I normally start locking down permissions on files (644 or 755 for most
things and making 544.544 owner of most files).
Here's the weird thing, though. When I followed the exact same procedure on
my laptop at home, I still get the errors.
Home laptop: Windows 2000 Pro on Dell Inspiron 3800.
Logged in as local user: holly with local administrative rights.
I can't figure this out.
----- Original Message -----
From: "Henry S. Thompson" <email@example.com>
Sent: Wednesday, January 10, 2001 11:54 AM
Subject: Re: [ANNOUNCEMENT] Updated: OpenSSH-2.3.0p1-1
> This still exhibits the crash behaviour I and others have been
> reporting for some time:
> [from a solaris box, to a cygwin sshd service]
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
More information about the Cygwin