Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Message-Id: <4.3.1.2.20011126213806.02161ef8@pop.ma.ultranet.com> X-Sender: lhall AT pop DOT ma DOT ultranet DOT com X-Mailer: QUALCOMM Windows Eudora Version 4.3.1 Date: Mon, 26 Nov 2001 21:52:21 -0500 To: "Collin Grady" , "Cygwin ML" From: "Larry Hall (RFK Partners, Inc)" Subject: Re: SSH/Bash error In-Reply-To: <015401c176e3$568c65e0$b4a1689e@MagusLaptop> References: <4 DOT 3 DOT 1 DOT 2 DOT 20011126172742 DOT 0214df18 AT pop DOT ma DOT ultranet DOT com> <4 DOT 3 DOT 1 DOT 2 DOT 20011126173538 DOT 020ea080 AT pop DOT ma DOT ultranet DOT com> <4 DOT 3 DOT 1 DOT 2 DOT 20011126190707 DOT 01656038 AT pop DOT ma DOT ultranet DOT com> <4 DOT 3 DOT 1 DOT 2 DOT 20011126192440 DOT 020ef828 AT pop DOT ma DOT ultranet DOT com> <4 DOT 3 DOT 1 DOT 2 DOT 20011126193649 DOT 020fb930 AT pop DOT ma DOT ultranet DOT com> <4 DOT 3 DOT 1 DOT 2 DOT 20011126195446 DOT 020f11e0 AT pop DOT ma DOT ultranet DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" The output clearly shows that the sshd that you're running is version 1.2.26. That's very old and not what is currently installed by Cygwin. This is the reason that you're having trouble connecting to your local machine. You need to get rid of whatever odd version of sshd you're running and put the Cygwin version in its place. I trust this is enough information for you to resolve your problem now. Regardless, I'm definitely getting the impression that your heart has not been in this debugging process. If you should have additional questions or observations regarding your local configuration of ssh, I think I'll opt to let someone else help you with it. I really don't have the time or the interest to try to help someone that puts no effort of their own into resolving problems they're having. Others on the list might have more tolerance for this though. I'll leave you in their capable hands. Good luck, Larry Hall lhall AT rfk DOT com RFK Partners, Inc. http://www.rfk.com 838 Washington Street (508) 893-9779 - RFK Office Holliston, MA 01746 (508) 893-9889 - FAX At 08:32 PM 11/26/2001, Collin Grady wrote: >I don't see how this helps at all, but here is ssh -v. > >[Administrator AT MAGUS-LAPTOP /bin]$ ssh -v -p 113 localhost >OpenSSH_3.0.1p1, SSH protocols 1.5/2.0, OpenSSL 0x0090602f >debug1: Reading configuration data /etc/ssh_config >debug1: Seeding random number generator >debug1: Rhosts Authentication disabled, originating port will not be >trusted. >debug1: restore_uid >debug1: ssh_connect: getuid 500 geteuid 500 anon 1 >debug1: Connecting to localhost [127.0.0.1] port 113. >debug1: temporarily_use_uid: 500/513 (e=500) >debug1: restore_uid >debug1: temporarily_use_uid: 500/513 (e=500) >debug1: restore_uid >debug1: Connection established. >debug1: identity file /home/Administrator/.ssh/identity type -1 >debug1: identity file /home/Administrator/.ssh/id_rsa type -1 >debug1: identity file /home/Administrator/.ssh/id_dsa type -1 >debug1: Remote protocol version 1.5, remote software version 1.2.26 >debug1: no match: 1.2.26 >debug1: Local version string SSH-1.5-OpenSSH_3.0.1p1 >debug1: Waiting for server public key. >debug1: Received server public key (768 bits) and host key (1024 bits). >debug1: Host 'localhost' is known and matches the RSA1 host key. >debug1: Found key in /home/Administrator/.ssh/known_hosts:2 >debug1: Encryption type: 3des >debug1: Sent encrypted session key. >debug1: Installing crc compensation attack detector. >debug1: Received encrypted confirmation. >debug1: Trying rhosts or /etc/hosts.equiv with RSA host authentication. >debug1: Server refused our rhosts authentication or host key. >debug1: Doing password authentication. >Administrator AT localhost's password: >debug1: Requesting pty. >debug1: Requesting shell. >debug1: Entering interactive session. >/bin/bash: Permission denied >Connection to localhost closed. >debug1: Transferred: stdin 0, stdout 30, stderr 33 bytes in 0.0 seconds >debug1: Bytes per second: stdin 0.0, stdout 600.0, stderr 660.0 >debug1: Exit status 1 >[Administrator AT MAGUS-LAPTOP /bin]$ > -Collin Grady > >Plan to be spontaneous - tomorrow. > >----- Original Message ----- >From: "Larry Hall (RFK Partners, Inc)" >To: "Collin Grady" ; "Cygwin ML" >Sent: Monday, November 26, 2001 5:00 PM >Subject: Re: SSH/Bash error > > > > No, I understand you perfectly. The fact that you can ssh to other > > machines is inconsequential in your debugging. You want to make sure > > that things are set up properly to allow you to ssh *into* your machine. > > Regardless, there's no magic pill here. You need to debug this and the > > steps I suggested will help you do that. It's worth the effort >considering > > the alternative. > > > > Larry Hall lhall AT rfk DOT com > > RFK Partners, Inc. http://www.rfk.com > > 838 Washington Street (508) 893-9779 - RFK Office > > Holliston, MA 01746 (508) 893-9889 - FAX > > > > > > > > At 07:46 PM 11/26/2001, Collin Grady wrote: > > > I think you're misunderstanding my problem. I can ssh to anywhere > > >except localhost. The sshd is returning the /bin/bash permission denied > > >when I ssh to localhost, whereas I can ssh to, say, a local campus server > > >and it works. Trying to ssh back to home comp does not work, however. > > > -Collin Grady > > > > > >Programmers don't die, they just GOSUB without RETURN. > > > > > >----- Original Message ----- > > >From: "Larry Hall (RFK Partners, Inc)" > > >To: "Collin Grady" ; "Cygwin ML" > > > >Sent: Monday, November 26, 2001 4:40 PM > > >Subject: Re: SSH/Bash error > > > > > > > > > > OK, so do you have /bin/bash in your environment before invoking ssh. > > > > You'll probably need to invoke ssh with its debugging turned on (-v > > > > see the ssh man page) to see where it's going wrong. I assume you > > > > read /usr/doc/Cygwin/openssh-*.README and followed all the >instructions > > > > there before attempting to use openssh? If not, go here and read this > > > > too. > > > > > > > > Larry Hall lhall AT rfk DOT com > > > > RFK Partners, Inc. http://www.rfk.com > > > > 838 Washington Street (508) 893-9779 - RFK Office > > > > Holliston, MA 01746 (508) 893-9889 - FAX > > > > > > > > > > > > > > > > At 07:35 PM 11/26/2001, Collin Grady wrote: > > > > > Thats the problem, I can't even get into ssh. > > > > > > > > > >[Administrator AT MAGUS-LAPTOP ~]$ ssh localhost > > > > >Administrator AT localhost's password: > > > > >/bin/bash: Permission denied > > > > >Connection to localhost closed. > > > > > -Collin Grady > > > > > > > > > >No one is listening until you make a mistake. > > > > > > > > > >----- Original Message ----- > > > > >From: "Larry Hall (RFK Partners, Inc)" > > > > >To: "Collin Grady" ; "Cygwin ML" > > > > > > > >Sent: Monday, November 26, 2001 4:30 PM > > > > >Subject: Re: SSH/Bash error > > > > > > > > > > > > > > > > OK, so compare these results with what you get via ssh. My guess >is > > > > > > that /bin/bash doesn't exist in that environment. If it does, you >may > > > > > > need to review your ssh configuration... > > > > > > > > > > > > Larry Hall lhall AT rfk DOT com > > > > > > RFK Partners, Inc. http://www.rfk.com > > > > > > 838 Washington Street (508) 893-9779 - RFK >Office > > > > > > Holliston, MA 01746 (508) 893-9889 - FAX > > > > > > > > > > > > >-- > > >Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple > > >Bug reporting: http://cygwin.com/bugs.html > > >Documentation: http://cygwin.com/docs.html > > >FAQ: http://cygwin.com/faq/ > > > > >-- >Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple >Bug reporting: http://cygwin.com/bugs.html >Documentation: http://cygwin.com/docs.html >FAQ: http://cygwin.com/faq/ -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/