From owner-freebsd-security@FreeBSD.ORG Mon Oct 28 19:57:08 2013 Return-Path: Delivered-To: freebsd-security@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id C2902C0 for ; Mon, 28 Oct 2013 19:57:08 +0000 (UTC) (envelope-from az@azsupport.com) Received: from as1.azsupport.com (azsupport.com [74.52.186.194]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id A38A22973 for ; Mon, 28 Oct 2013 19:57:08 +0000 (UTC) Received: from localhost (unknown [109.75.144.107]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by as1.azsupport.com (Postfix) with ESMTPSA id 9F6645D5 for ; Mon, 28 Oct 2013 20:57:00 +0100 (CET) Date: Mon, 28 Oct 2013 20:56:57 +0100 From: Andrei To: freebsd-security@freebsd.org Subject: Re: OpenPAM/SSHD privacy hole (FreeBSD 9.2+ affected) Message-ID: <20131028205657.4952673a@azsupport.com> In-Reply-To: <86ppqqmlij.fsf@nine.des.no> References: <20131023135408.38752099@azsupport.com> <1382529986.729788.498652166.90148.2@c-st.net> <86y55emw8a.fsf@nine.des.no> <8D7C4A668063437DBEEA0D513D51B662@multiplay.co.uk> <86ppqqmlij.fsf@nine.des.no> Organization: azsupport.com X-Mailer: Claws Mail 3.9.2 (GTK+ 2.24.19; amd64-portbld-freebsd10.0) Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Security issues \[members-only posting\]" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Oct 2013 19:57:08 -0000 On Sun, 27 Oct 2013 22:50:12 +0100 Dag-Erling Sm=C3=B8rgrav wrote: > "Steven Hartland" writes: > > Out of curiosity whats the reasoning behind it doing things? >=20 > Less confusion when proxying one SSH connection through another, for > one. FWIW, it mirrors what most Linux distros do. How about just IP as Linux do: az@az:~$ ssh test@1.2.3.4 test@1.2.3.4's password:=20 I think if you change the hostname to IP (without Linux style "'s" at the end of IP) in the default settings, in this case everyone will be happy. :) Kind regards, Andrei.