Re: SSH - Can't Login (3rd Post)
snip No, if it's reporting 1.7.1, I expect that's the version you're running. And I expect that's coming into play here. But go ahead and double check it in the Windows explorer. I expect you'll find it reports 1.7.1 too. This is a problem. I expect you know that you need to stop all your services before an upgrade in order to get the new DLL moved into place immediately, right? If you don't do this, it will queue up the move for next reboot. My guess is you've rebooted at least once since installing 1.7.x 1.7.1 but it's possible things have gotten gummed up if you didn't and have since done other upgrades (that's pure theory though). What's not is that you have ZoneAlarm installed that is known to cause problems. I'd recommend unstalling it, stopping all Cygwin services (cron, cygserver, httpd2, and sshd), reinstall the Cygwin package, and then restart the services. You should find this process gives you a current cygwin1.dll in '/bin'. If not, we need to look at the results of the installation process (and/or for http://cygwin.com/acronyms/#3PP ). Looks like the gummed up diagnosis was the correct one. I restarted my system in safe mode with networking and ran setup. It reported nothing needed to be updated (looks like setup has an issue with detecting differences between what is actually running, and what should be installed; but that is a different debate). I opened a Cygwin bash shell and ran the uname -a command and it still reported release 1.7.1, not 1.7.7. I reran the setup and reinstalled Cygwin and cygserver then rebooted the system back to its normal operations mode. Once the system was up and stable I restarted the bash shell and got a series of stack dumps with complaints about timing out waiting for a return from a long jump (another issue for another time). I closed the window and did the insane thing (repeated opening of a bash shell hoping for a different result). and this time I got a working shell prompt. I ran the uname -a command and this time it returned the 1.7.7 version. Next, I did an ssh to my own machine ssh ncc-1701 and was able to get the expected prompts for a login. Ssh appears to be working again. Thank you all for your help and suggestions. It is community support and cooperation, as well as support from the Dev team that keeps Cygwin one of the most popular *nix like environments for Windoze. Sincerely, Brian S. Wilson -- 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
Re: SSH - Can't Login (3rd Post)
On Thu, Oct 28, 2010 at 11:02 PM, Larry Hall (Cygwin) reply-to-list-only...@cygwin.com wrote: On 10/28/2010 10:37 PM, Brian Wilson wrote: The ssh command and its response are just a cut and paste of the bash screen. Trying to execute ssh -v ncc-1701 gives exactly the same results (note there is no -v option in the displayed list). $ ssh wil...@ncc-1701 usage: ssh [-1246AaCfgKkMNnqsTtVvXxYy] [-b bind_address] [-c cipher_spec]... ^ There it is. ;-) I really didn't doubt that you cut and paste the output once I looked at it but I'm glad you confirmed it. I've attached a new cygcheck output (-svr) as you suggested. One thing I noted was that the uname -a output says I have Cygwin 1.7.1 and this confuses me. I've updated on a regular basis and reboot whenever the installation requests me to do so. I should have the 1.7.7-1 release. The cygcheck seems to have differing 1.7* information. Is there some magic translation I need to know of to get the correct release number? No, if it's reporting 1.7.1, I expect that's the version you're running. And I expect that's coming into play here. But go ahead and double check it in the Windows explorer. I expect you'll find it reports 1.7.1 too. This is a problem. I expect you know that you need to stop all your services before an upgrade in order to get the new DLL moved into place immediately, right? If you don't do this, it will queue up the move for next reboot. My guess is you've rebooted at least once since installing 1.7.x 1.7.1 but it's possible things have gotten gummed up if you didn't and have since done other upgrades (that's pure theory though). What's not is that you have ZoneAlarm installed that is known to cause problems. I'd recommend unstalling it, stopping all Cygwin services (cron, cygserver, httpd2, and sshd), reinstall the Cygwin package, and then restart the services. You should find this process gives you a current cygwin1.dll in '/bin'. If not, we need to look at the results of the installation process (and/or for http://cygwin.com/acronyms/#3PP ). -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 _ A: Yes. Q: Are you sure? A: Because it reverses the logical flow of conversation. Q: Why is top posting annoying in email? -- 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 I'm pretty convinced there's something going on (or NOT going on...) during the upgrade process. I've seen this report of someone doing a setup and still having an old cygwin1.dll, it's happened to me (see thread regarding svn metadata name mangling), and I've had someone email me about the name mangling issue (who didn't want to post to the list) discover he had a downlevel version of the cygwin1.dll file also. There's also the additional evidence of finding a half dozen or so files ending in .new /usr/bin and /usr/sbin. Perhaps Microsoft had a hotfix or somesuch that might have affected Cygwin when it needs to do a replace files on boot thing. I have no idea how that's implemented, so that's speculation, of course. --jc -- 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
Re: SSH - Can't Login (3rd Post)
On 10/28/2010 10:37 PM, Brian Wilson wrote: The ssh command and its response are just a cut and paste of the bash screen. Trying to execute ssh -v ncc-1701 gives exactly the same results (note there is no -v option in the displayed list). $ ssh wil...@ncc-1701 usage: ssh [-1246AaCfgKkMNnqsTtVvXxYy] [-b bind_address] [-c cipher_spec]... ^ There it is. ;-) Oh, that -v option... ;-) cygcheck seems to have differing 1.7* information. Is there some magic translation I need to know of to get the correct release number? No, if it's reporting 1.7.1, I expect that's the version you're running. And I expect that's coming into play here. But go ahead and double check it in the Windows explorer. I expect you'll find it reports 1.7.1 too. This is a problem. I expect you know that you need to stop all your services before an upgrade in order to get the new DLL moved into place immediately, right? If you don't do this, it will queue up the move for next reboot. My guess is you've rebooted at least once since installing 1.7.x 1.7.1 but it's possible things have gotten gummed up if you didn't and have since done other upgrades (that's pure theory though). What's not is that you have ZoneAlarm installed that is known to cause problems. I'd recommend unstalling it, stopping all Cygwin services (cron, cygserver, httpd2, and sshd), reinstall the Cygwin package, and then restart the services. You should find this process gives you a current cygwin1.dll in '/bin'. If not, we need to look at the results of the installation process (and/or for http://cygwin.com/acronyms/#3PP ). I know cygcheck is reporting Zone Alarm, but I've never had Zone Alarm installed on my system. I do have McAfee installed, but have never had a problem with it blocking an installation. I tried to reinstall just the cygwin application last night and rebooted immediately; but still I see the same information from cygcheck. I will work this again tonight and try installing from reboot to safe mode and reinstall to see if that makes a difference. I don't always stop all services before a restart and have relied on the reboot to take care of any issues with updating running processes. Perhaps that is not wise. -- 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
Re: SSH - Can't Login (3rd Post)
I have the same problem and have not been able to resolve the issue either. I get the following from the type -a command. Invoking either [ssh version] from the bash shell with a complete path still just displays the usage message and gives a return code of 255. Everything else seems to be working fine. Brian S. wil...@ncc-1701 ~ $ type -a ssh ssh is /usr/bin/ssh ssh is /bin/ssh A return code of 255 seems odd. Maybe a required DLL is missing. What is the complete usage message displayed? What is the output of the following: ls -l /usr/bin/ssh /bin/ssh ldd /usr/bin/ssh What happens when you invoke ssh from a cmd shell? Brian S. wil...@ncc-1701 ~ $ ls -l /usr/bin/ssh /bin/ssh -rwxr-xr-x 1 Brian S. Wilson root 342030 2010-09-03 04:44 /bin/ssh -rwxr-xr-x 1 Brian S. Wilson root 342030 2010-09-03 04:44 /usr/bin/ssh Brian S. wil...@ncc-1701 ~ $ ldd /usr/bin/ssh ntdll.dll = /cygdrive/c/WINDOWS/system32/ntdll.dll (0x7c90) kernel32.dll = /cygdrive/c/WINDOWS/system32/kernel32.dll (0x7c80) cygcrypto-0.9.8.dll = /usr/bin/cygcrypto-0.9.8.dll (0x6ba4) cygwin1.dll = /usr/bin/cygwin1.dll (0x6100) ADVAPI32.DLL = /cygdrive/c/WINDOWS/system32/ADVAPI32.DLL (0x77dd) RPCRT4.dll = /cygdrive/c/WINDOWS/system32/RPCRT4.dll (0x77e7) Secur32.dll = /cygdrive/c/WINDOWS/system32/Secur32.dll (0x77fe) cyggcc_s-1.dll = /usr/bin/cyggcc_s-1.dll (0x67f0) cygz.dll = /usr/bin/cygz.dll (0x692c) cygssp-0.dll = /usr/bin/cygssp-0.dll (0x6728) $ ls -l /cygdrive/c/WINDOWS/system32/ntdll.dll /cygdrive/c/WINDOWS/system32/kernel32.dll /usr/bin/cygcrypto- 0.9.8.dll /usr/bin/cygwin1.dll /cygdrive/c/WINDOWS/system32/ADVAPI32.DLL /cygdrive/c/WINDOWS/system32/RPCRT4.dll /cygdrive/c/WINDOWS/system32/Secur32.dll /usr/bin/cyggcc_s-1.dll /usr/bin/cygz.dll /usr/bin/cygssp-0.dll -rwxrwx---+ 1 Administrators SYSTEM 714752 2009-02-09 07:10 /cygdrive/c/WINDOWS/system32/ntdll.dll -rwxrwx---+ 1 Administrators SYSTEM 989696 2009-03-21 10:06 /cygdrive/c/WINDOWS/system32/kernel32.dll -rwxr-xr-x 1 Brian S. Wilson root 1174030 2009-11-05 12:49 /usr/bin/cygcrypto-0.9.8.dll -rwxr-xr-x 1 Brian S. Wilson root 2477372 2009-12-07 05:51 /usr/bin/cygwin1.dll -rwxrwx---+ 1 Administrators SYSTEM 617472 2009-02-09 07:10 /cygdrive/c/WINDOWS/system32/ADVAPI32.DLL -rwxrwx---+ 1 Administrators SYSTEM 590848 2010-08-16 04:45 /cygdrive/c/WINDOWS/system32/RPCRT4.dll -rwxrwx---+ 1 Administrators SYSTEM 56832 2009-06-25 04:25 /cygdrive/c/WINDOWS/system32/Secur32.dll -rwxr-xr-x 1 Brian S. Wilson root 46094 2009-12-11 03:23 /usr/bin/cyggcc_s-1.dll -rwxr-xr-x 1 Brian S. Wilson root 65536 2009-03-01 20:34 /usr/bin/cygz.dll -rwxr-xr-x 1 Brian S. Wilson root 10254 2009-12-11 03:24 /usr/bin/cygssp-0.dll Brian S. wil...@ncc-1701 ~ $ ssh wil...@ncc-1701 usage: ssh [-1246AaCfgKkMNnqsTtVvXxYy] [-b bind_address] [-c cipher_spec] [-D [bind_address:]port] [-e escape_char] [-F configfile] [-I pkcs11] [-i identity_file] [-L [bind_address:]port:host:hostport] [-l login_name] [-m mac_spec] [-O ctl_cmd] [-o option] [-p port] [-R [bind_address:]port:host:hostport] [-S ctl_path] [-W host:port] [-w local_tun[:remote_tun]] [u...@]hostname [command] Brian S. wil...@ncc-1701 ~ $ echo $? 255 I get the same message from a DOS command shell when I cd to /cygwin/bin and execute ssh directly. I've also attached the output of a cygcheck which did show a few issues I was not aware of and which I will work on correcting this weekend; but which shouldn't affect ssh's operations (as far as I am aware). cygcheck.out Description: Binary data -- 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
Re: SSH - Can't Login (3rd Post)
On 10/28/2010 8:39 AM, Brian Wilson wrote: $ ssh wil...@ncc-1701 usage: ssh [-1246AaCfgKkMNnqsTtVvXxYy] [-b bind_address] [-c cipher_spec] [-D [bind_address:]port] [-e escape_char] [-F configfile] [-I pkcs11] [-i identity_file] [-L [bind_address:]port:host:hostport] [-l login_name] [-m mac_spec] [-O ctl_cmd] [-o option] [-p port] [-R [bind_address:]port:host:hostport] [-S ctl_path] [-W host:port] [-w local_tun[:remote_tun]] [u...@]hostname [command] Brian S. wil...@ncc-1701 ~ $ echo $? 255 If that is a direct return of a Win32 error then: $ net helpmsg 255 The extended attributes are inconsistent. You may have better luck getting to the bottom of this by running the server with debug turned on and running the client with verbose flags turned completely on. If you find something when doing that which you want to follow-up on the list, please send exactly what you did, what you saw, and your cygcheck output (-srv) to the list (see http://cygwin.com/problems.html for details). If you really are getting stuck when parsing the input, then you might find that comparing the output of the old and new ssh output when running under strace shows you something. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 _ A: Yes. Q: Are you sure? A: Because it reverses the logical flow of conversation. Q: Why is top posting annoying in email? -- 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
Re: SSH - Can't Login (3rd Post)
On 10/28/2010 10:37 PM, Brian Wilson wrote: The ssh command and its response are just a cut and paste of the bash screen. Trying to execute ssh -v ncc-1701 gives exactly the same results (note there is no -v option in the displayed list). $ ssh wil...@ncc-1701 usage: ssh [-1246AaCfgKkMNnqsTtVvXxYy] [-b bind_address] [-c cipher_spec]... ^ There it is. ;-) I really didn't doubt that you cut and paste the output once I looked at it but I'm glad you confirmed it. I've attached a new cygcheck output (-svr) as you suggested. One thing I noted was that the uname -a output says I have Cygwin 1.7.1 and this confuses me. I've updated on a regular basis and reboot whenever the installation requests me to do so. I should have the 1.7.7-1 release. The cygcheck seems to have differing 1.7* information. Is there some magic translation I need to know of to get the correct release number? No, if it's reporting 1.7.1, I expect that's the version you're running. And I expect that's coming into play here. But go ahead and double check it in the Windows explorer. I expect you'll find it reports 1.7.1 too. This is a problem. I expect you know that you need to stop all your services before an upgrade in order to get the new DLL moved into place immediately, right? If you don't do this, it will queue up the move for next reboot. My guess is you've rebooted at least once since installing 1.7.x 1.7.1 but it's possible things have gotten gummed up if you didn't and have since done other upgrades (that's pure theory though). What's not is that you have ZoneAlarm installed that is known to cause problems. I'd recommend unstalling it, stopping all Cygwin services (cron, cygserver, httpd2, and sshd), reinstall the Cygwin package, and then restart the services. You should find this process gives you a current cygwin1.dll in '/bin'. If not, we need to look at the results of the installation process (and/or for http://cygwin.com/acronyms/#3PP ). -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 _ A: Yes. Q: Are you sure? A: Because it reverses the logical flow of conversation. Q: Why is top posting annoying in email? -- 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
Re: SSH - Can't Login (3rd Post)
The critical information is that ssh works fine by using setup.exe to back-configure version 5.5p?.? (the previous version) with no other changes. Completely reliably, for different users on different machines. -- 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
Re: SSH - Can't Login (3rd Post)
On Wed, Oct 27, 2010 at 4:02 AM, Charles Smith cts.priv...@yahoo.com wrote: The critical information is that ssh works fine by using setup.exe to back-configure version 5.5p?.? (the previous version) with no other changes. Completely reliably, for different users on different machines. -- 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 I ran into this also, the other day. Check the cygwin1.dll version (with cygcheck). --jc -- 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
Re: SSH - Can't Login (3rd Post)
I'm apparently having the same problem you are - when I run the ssh client, it gives me the usage output. I discovered that if I go back to the previous version (5.5p1.2?), it works. Every time I update with setup.exe, I have to go back and reset openssh to 5.5. I figured I must be doing something really stupid, until a colleague complained to me that ssh didn't work - when I told him about the 5.5 version, that solved his problem. This has been going on for months now. I do an internet search occasionally, but nothing comes up. I'm actually quite puzzled. -- 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
Re: SSH - Can't Login (3rd Post)
On 10/26/2010 1:53 PM, Charles Smith wrote: I'm apparently having the same problem you are - when I run the ssh client, it gives me the usage output. I discovered that if I go back to the previous version (5.5p1.2?), it works. Every time I update with setup.exe, I have to go back and reset openssh to 5.5. I figured I must be doing something really stupid, until a colleague complained to me that ssh didn't work - when I told him about the 5.5 version, that solved his problem. This has been going on for months now. I do an internet search occasionally, but nothing comes up. I'm actually quite puzzled. Have you tried to confirm that you don't have an alias, shell function, or script named ssh that is masking the real ssh binary? Something like that could be calling the real ssh with some arguments that are invalid under the latest version. What do you get when you run the following: type -a ssh Have you tried installing a fresh copy of Cygwin to a new directory to see if the problem recurs in that instance? If the problem happens in one but not the other when they should be otherwise identical, a diff over the directories might track down the problem. If the problem happens in both places, maybe you have some other software installed on your system that is somehow interfering. -Jeremy -- 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
Re: SSH - Can't Login (3rd Post)
On 10/26/2010 1:53 PM, Charles Smith wrote: I'm apparently having the same problem you are - when I run the ssh client, it gives me the usage output. I discovered that if I go back to the previous version (5.5p1.2?), it works. Every time I update with setup.exe, I have to go back and reset openssh to 5.5. I figured I must be doing something really stupid, until a colleague complained to me that ssh didn't work - when I told him about the 5.5 version, that solved his problem. This has been going on for months now. I do an internet search occasionally, but nothing comes up. I'm actually quite puzzled. Have you tried to confirm that you don't have an alias, shell function, or script named ssh that is masking the real ssh binary? Something like that could be calling the real ssh with some arguments that are invalid under the latest version. What do you get when you run the following: type -a ssh Have you tried installing a fresh copy of Cygwin to a new directory to see if the problem recurs in that instance? If the problem happens in one but not the other when they should be otherwise identical, a diff over the directories might track down the problem. If the problem happens in both places, maybe you have some other software installed on your system that is somehow interfering. I have the same problem and have not been able to resolve the issue either. I get the following from the type -a command. Invoking either from the bash shell with a complete path still just displays the usage message and gives a return code of 255. Everything else seems to be working fine. Brian S. wil...@ncc-1701 ~ $ type -a ssh ssh is /usr/bin/ssh ssh is /bin/ssh Brian S. Wilson -- 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
Re: SSH - Can't Login (3rd Post)
On 10/26/2010 09:10 PM, Brian Wilson wrote: I have the same problem and have not been able to resolve the issue either. I get the following from the type -a command. Invoking either from the bash shell with a complete path still just displays the usage message and gives a return code of 255. Everything else seems to be working fine. A return code of 255 seems odd. Maybe a required DLL is missing. What is the complete usage message displayed? Brian S. wil...@ncc-1701 ~ $ type -a ssh ssh is /usr/bin/ssh ssh is /bin/ssh What is the output of the following: ls -l /usr/bin/ssh /bin/ssh ldd /usr/bin/ssh What happens when you invoke ssh from a cmd shell? -Jeremy -- 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
Re: SSH - Can't Login (3rd Post)
I checked the following below. The user's home directory has the proper permissions (755), the .ssh directory is 700, and the files underneath the .ssh directory is 600. By default StrictModes is set to no. I still can't log in. Any help will be greatly appreciated. Thanks, and regards, Mr. Auteria W. Winzer Jr. - Original Message From: Slide slide.o@gmail.com To: cygwin@cygwin.com Sent: Sat, August 28, 2010 4:56:30 PM Subject: Re: SSH - Can't Login (3rd Post) On Sat, Aug 28, 2010 at 4:34 PM, Auteria W. Winzer Jr. wwin...@yahoo.com wrote: I've posted this 3 times now. I'm wondering if anyone from the Cygwin staff is receiving it. I've been an outstanding member of the mailing list for a very long time. Anyway, here's my issue: I've set up SSH with no problems in the past, yet when I try to log into itself I get the following: snip Check the following: ls -la /home/USER/.ssh ls -la /home Does the .ssh folder have permissions 700 and files within 600? Do you have StrictModes yes in your sshd_conf file? If so, then the server will ignore the keys in the .ssh sub-directory if the home directory is writeable by anyone other than the Owner. slide -- 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 -- 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
Re: SSH - Can't Login (3rd Post)
On Mon, Aug 30, 2010 at 18:03, Auteria W. Winzer Jr. wrote: I checked the following below. The user's home directory has the proper permissions (755), the .ssh directory is 700, and the files underneath the .ssh directory is 600. By default StrictModes is set to no. I still can't log in. Any help will be greatly appreciated. Help us helping you. Begin by posting a relevant part of the SERVER side log, with at least a DEBUG1 level. Also the requested information as stated in http://cygwin.com/problems.html might be useful... -- 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 Regards, ___ Julio Costa -- 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
SSH - Can't Login (3rd Post)
I've posted this 3 times now. I'm wondering if anyone from the Cygwin staff is receiving it. I've been an outstanding member of the mailing list for a very long time. Anyway, here's my issue: I've set up SSH with no problems in the past, yet when I try to log into itself I get the following: # ssh -v ca53...@localhost OpenSSH_5.6p1, OpenSSL 0.9.8o 01 Jun 2010 debug1: Reading configuration data /etc/ssh_config debug1: Connecting to localhost [127.0.0.1] port 22. debug1: Connection established. debug1: permanently_set_uid: 0/544 debug1: identity file /home/ca53918/.ssh/id_rsa type 1 debug1: identity file /home/ca53918/.ssh/id_rsa-cert type -1 debug1: identity file /home/ca53918/.ssh/id_dsa type 2 debug1: identity file /home/ca53918/.ssh/id_dsa-cert type -1 debug1: Remote protocol version 2.0, remote software version OpenSSH_5.6 debug1: match: OpenSSH_5.6 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_5.6 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server-client aes128-ctr hmac-md5 none debug1: kex: client-server aes128-ctr hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(102410248192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY The authenticity of host 'localhost (127.0.0.1)' can't be established. RSA key fingerprint is Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added 'localhost' (RSA) to the list of known hosts. debug1: ssh_rsa_verify: signature correct debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: Roaming not allowed by server debug1: SSH2_MSG_SERVICE_REQUEST sent debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey,password,keyboard-interactive debug1: Next authentication method: publickey debug1: Offering RSA public key: /home/ca53918/.ssh/id_rsa Connection closed by 127.0.0.1 There's an immediate connection. The sshd service is running, and I've used both the ssh_user_config and ssh_host_config script to set up the environment. All the appropriate files look clean underneath my .ssh directory. Any help will be greatly appreciated. Thanks, and regards, Auteria W. Winzer Jr. -- 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
Re: SSH - Can't Login (3rd Post)
On Sat, Aug 28, 2010 at 4:34 PM, Auteria W. Winzer Jr. wwin...@yahoo.com wrote: I've posted this 3 times now. I'm wondering if anyone from the Cygwin staff is receiving it. I've been an outstanding member of the mailing list for a very long time. Anyway, here's my issue: I've set up SSH with no problems in the past, yet when I try to log into itself I get the following: snip Check the following: ls -la /home/USER/.ssh ls -la /home Does the .ssh folder have permissions 700 and files within 600? Do you have StrictModes yes in your sshd_conf file? If so, then the server will ignore the keys in the .ssh sub-directory if the home directory is writeable by anyone other than the Owner. slide -- 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
