From owner-freebsd-security Fri Jan 26 12:38: 6 2001 Delivered-To: freebsd-security@freebsd.org Received: from mail.zuhause.org (zuhause.org [205.215.217.178]) by hub.freebsd.org (Postfix) with ESMTP id 7952A37B69C for ; Fri, 26 Jan 2001 12:37:45 -0800 (PST) Received: by mail.zuhause.org (Postfix, from userid 1001) id 8C2967C83; Fri, 26 Jan 2001 14:37:44 -0600 (CST) From: Bruce Albrecht MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14961.57367.549780.51395@localhost.zuhause.org> Date: Fri, 26 Jan 2001 14:37:43 -0600 (CST) To: Dan Debertin Cc: Subject: Re: wierd ssh failure In-Reply-To: References: <14961.56948.936058.387747@localhost.zuhause.org> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Dan Debertin writes: > On Fri, 26 Jan 2001, Bruce Albrecht wrote: > > I forgot to mention that I'm running 4.2-stable (circa last week). > > When I ran strings on sshd, I couldn't find the message that I got > > from ssh, which is why I'm wondering if this was a temporary routing > > error, or an attempt to do a man-in-the-middle attack. > > Run strings on your client; that's where it's coming from: > kidjo [02:32pm] # strings /usr/bin/ssh | grep away > You don't exist, go away! > > I've gotten that message when playing around with NIS; it looked like the > SSH client couldn't tell who I was when I ran it, so it quit. I don't > think you've been cracked; ssh just can't tell who you are. Thanks. I thought it was coming from the server side, didn't think it was a client-side issue. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message