From owner-freebsd-bugs@FreeBSD.ORG Mon Dec 1 12:47:30 2014 Return-Path: Delivered-To: freebsd-bugs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 757EADAD for ; Mon, 1 Dec 2014 12:47:30 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 41F12A01 for ; Mon, 1 Dec 2014 12:47:30 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id sB1ClUtb064194 for ; Mon, 1 Dec 2014 12:47:30 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 195554] New: ssh tries an explicit key _after_ key agent keys Date: Mon, 01 Dec 2014 12:47:30 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: avg@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Dec 2014 12:47:30 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195554 Bug ID: 195554 Summary: ssh tries an explicit key _after_ key agent keys Product: Base System Version: 11.0-CURRENT Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: bin Assignee: freebsd-bugs@FreeBSD.org Reporter: avg@FreeBSD.org I wonder if the way ssh behaves is sane in the following situation. I have ssh-agent running and there is a number of keys added to it. Then I run ssh -i foo bar and what I see is that ssh first tries the keys from the agent rather than foo. But in this case I get "Too many authentication failures" before the explicit key is even tried. if I unset SSH_AGENT_PID and SSH_AUTH_SOCK then everything is okay, obviously. Redacted output of ssh -vv: debug2: key: /home/avg/.ssh/id_dsa (0x8038163c0), debug2: key: /home/avg/.ssh/id_dsa_xxx (0x803816440), debug2: key: /home/avg/.ssh/id_dsa_yyy (0x8038164c0), debug2: key: /home/avg/.ssh/zzz (0x803816540), debug2: key: /home/avg/.ssh/vvv (0x8038165c0), debug2: key: /home/avg/.ssh/www (0x803816640), debug2: key: /usr/local/lib/ruby/gems/2.0/gems/vagrant-1.6.5/keys/vagrant (0x803816100), explicit debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic,password debug1: Next authentication method: publickey debug1: Offering DSA public key: /home/avg/.ssh/id_dsa ... debug1: Offering RSA public key: /home/avg/.ssh/www debug2: we sent a publickey packet, wait for reply Received disconnect from x.x.x.x: 2: Too many authentication failures for avg -- You are receiving this mail because: You are the assignee for the bug.