From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 89564 invoked by alias); 19 Dec 2016 03:40:45 -0000 Mailing-List: contact overseers-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: , Sender: overseers-owner@sourceware.org Received: (qmail 89540 invoked by uid 89); 19 Dec 2016 03:40:43 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-4.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,RP_MATCHES_RCVD,SPF_PASS autolearn=ham version=3.3.2 spammy=guessing, Hx-spam-relays-external:sk:mail.pa, H*RU:sk:mail.pa, Hx-languages-length:755 X-HELO: mail.pacific.net Received: from mail.pacific.net (HELO mail.pacific.net) (208.106.118.17) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 19 Dec 2016 03:40:33 +0000 Received: from [192.168.1.100] (70-36-232-57.dsl.dynamic.fusionbroadband.com [70.36.232.57]) (authenticated bits=0) by mail.pacific.net (8.14.4/8.14.4) with ESMTP id uBJ3eSbZ021704 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Sun, 18 Dec 2016 19:40:29 -0800 To: overseers@sourceware.org Cc: Joseph Myers From: Rical Jasan Subject: SSH Authentication Failures Message-ID: Date: Mon, 19 Dec 2016 03:40:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Null-Tag: 131c115648b4603430c41aa7ee41bfd7 X-SW-Source: 2016-q4/txt/msg00111.txt.bz2 Hi, Sorry it's taken so long to get to this, but I'm having trouble logging in to my new account, rj@sourceware.org. $ /bin/date; ssh sourceware.org Sun Dec 18 19:33:26 PST 2016 Permission denied (publickey). Not that I expect to have a shell, just showing the problem. Debug output doesn't show anything more helpful than that result. Could you take a look at the log and see why it's failing? I have the User and IdentityFile under a Host section for sourceware.org in ~/.ssh/config. I'm pretty sure I gave you the right public key, because ssh tries all the keys it can find when they fail, and they all failed, so I'm guessing it's something else, and the server logs are generally more informative. Thank you, Rical