X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:message-id:date:from:reply-to:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; q=dns; s=default; b=rjyDpv4TZacNo/UF DNsTxTfHnHKws3xYh7sYMujo2Dyb9uvdhq3ccRCp7S35+pFR6wSE0tvoJ+jCND+c 473FAafISk8O0irI0jcQN23SDG6vVxH3oYDrd6YdmvJcFYer7XkFyRvKksHWKoF7 /tYeG0LXAXEXsPmIDzkMO5noPmQ= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:message-id:date:from:reply-to:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; s=default; bh=EHuuC99Ox8c0mC9+KW2eQc BuaLk=; b=wSVfQJoEURFu5+vKJrcZMJIrDmG6ZHVnWI5OXb9MHrD5lVLlJEtojT DTEvCaF52sca0CtW4wMuxKAjICZyAM+DwMmLY+KU68qEnX/7nUS3DGEOvZ+fFcIe FumJZxMR/sJUEsIjmT8Usdyfmw3dj4kLUN6W5yx4NB/az5JSzU+4w= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=0.7 required=5.0 tests=AWL,BAYES_50,SPF_HELO_PASS,SPF_PASS,T_RP_MATCHES_RCVD autolearn=ham version=3.3.2 X-HELO: smtp.jhmg.net Message-ID: <5573B0E0.4010304@jhmg.net> Date: Sat, 06 Jun 2015 19:48:00 -0700 From: Jim Garrison Reply-To: jhg AT acm DOT org User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: I can't connect to ssh References: <1472212892 DOT 10172358 DOT 1433639713084 DOT JavaMail DOT yahoo AT mail DOT yahoo DOT com> In-Reply-To: <1472212892.10172358.1433639713084.JavaMail.yahoo@mail.yahoo.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit On 6/6/2015 6:15 PM, Marilo wrote: > > > harvey AT samsung350 ~ > $ nc 127.0.0.1 22 > SSH-2.0-OpenSSH_6.6.1 > > > harvey AT samsung350 ~ > $ ssh 127.0.0.1 > Connection closed by 127.0.0.1 > > > I have no authorized_keys file which is fine. I am allowing PasswordAuthentication and also PubKeyAuthentication on the server. > My password is not empty. > > It is not prompting me for any password. It just straight away says "connection closed by 127.0.0.1" > > I don't have any other computers on the network that I can try from at the moment. [snip] Check the permissions on the public key file and authorized_keys in ~/.ssh (and the .ssh directory itself). If the target were Linux you could also look in /var/log/secure to see why the remote closed the connection. On a cygwin remote system I don't know where the log is located, but somebody else on the list can probably tell you. -- Jim Garrison (jhg AT acm DOT org) PGP Keys at http://www.jhmg.net RSA 0x04B73B7F DH 0x70738D88 -- 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