From owner-freebsd-security@FreeBSD.ORG Fri Oct 2 01:16:30 2009 Return-Path: Delivered-To: freebsd-security@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8063B1065672 for ; Fri, 2 Oct 2009 01:16:30 +0000 (UTC) (envelope-from wollman@hergotha.csail.mit.edu) Received: from hergotha.csail.mit.edu (hergotha.csail.mit.edu [66.92.79.170]) by mx1.freebsd.org (Postfix) with ESMTP id 0178B8FC21 for ; Fri, 2 Oct 2009 01:16:29 +0000 (UTC) Received: from hergotha.csail.mit.edu (localhost [127.0.0.1]) by hergotha.csail.mit.edu (8.14.3/8.14.3) with ESMTP id n920oNmX012010; Thu, 1 Oct 2009 20:50:23 -0400 (EDT) (envelope-from wollman@hergotha.csail.mit.edu) Received: (from wollman@localhost) by hergotha.csail.mit.edu (8.14.3/8.14.3/Submit) id n920oNab012007; Thu, 1 Oct 2009 20:50:23 -0400 (EDT) (envelope-from wollman) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <19141.20047.694147.865710@hergotha.csail.mit.edu> Date: Thu, 1 Oct 2009 20:50:23 -0400 From: Garrett Wollman To: johnea In-Reply-To: <4AC545C3.9020608@johnea.net> References: <4AC545C3.9020608@johnea.net> X-Mailer: VM 7.17 under 21.4 (patch 21) "Educational Television" XEmacs Lucid X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (hergotha.csail.mit.edu [127.0.0.1]); Thu, 01 Oct 2009 20:50:23 -0400 (EDT) X-Spam-Status: No, score=-1.4 required=5.0 tests=ALL_TRUSTED autolearn=disabled version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on hergotha.csail.mit.edu X-Mailman-Approved-At: Fri, 02 Oct 2009 03:00:09 +0000 Cc: freebsd-security@freebsd.org Subject: openssh concerns X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Security issues \[members-only posting\]" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Oct 2009 01:16:30 -0000 < said: > The thing that concerned me is an entry I saw in netstat showing > my system connecting back to a machine that was attempting to log > in to ssh. > Does the ssh server establish a socket to a client attempting login? The SSH protocol does not, but you appear to be using "TCP wrappers" (/etc/hosts.allow) configured in such a way that it make an IDENT protocol request back to the originating server. This is rarely likely to do anything useful and should probably be disabled. > tcp4 0 0 atom.60448 host154.advance.com.ar.auth TIME_WAIT "auth" is the port number used by the IDENT protocol. -GAWollman