Date: Tue, 05 Jan 1999 14:15:38 -0800 From: bmah@CA.Sandia.GOV (Bruce A. Mah) To: The Hermit Hacker <scrappy@hub.org> Cc: freebsd-security@FreeBSD.ORG Subject: Re: ssh "error" message .. Message-ID: <199901052215.OAA19362@stennis.ca.sandia.gov> In-Reply-To: Your message of "Tue, 05 Jan 1999 17:45:05 -0400." <Pine.BSF.4.05.9901051744120.18250-100000@thelab.hub.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--==_Exmh_-361153620P Content-Type: text/plain; charset=us-ascii If memory serves me right, The Hermit Hacker wrote: > Has anyone seen the following before? I'm thinking a port-attack, since > I've gotten two reports so far, each reporting the same host, but > different IP... > > hub> logout > Waiting for forwarded connections to terminate... > The following connections are open: > X11 connection from tntport0581.cwjamaica.com port 1488 > X11 connection from tntport0581.cwjamaica.com port 1918 Yes, many many times. These are the error messages that you see when you ssh to another machine, fire up some X clients on the remote host, then try to logout. The X protocol messages from the X clients are tunneled over the encrypted SSH connection, so the SSH connection can't go away without killing the clients. The behavior you see gives you (the user) a chance to gracefully shut down the X clients first. If I don't care about those X clients, I'll usually kill the window from which I ran ssh. Bruce. --==_Exmh_-361153620P Content-Type: application/pgp-signature -----BEGIN PGP MESSAGE----- Version: 2.6.2 iQCVAwUBNpKPCajOOi0j7CY9AQEbTAP/S3j8mTse65K58z1TLHKOpoqrdhuYBRtt gDN10m4+icrf75yO3/AyYVHS4TwyL8/14Gck7w95c2ShIQz7HxE3eu9mq5dUYRdy h0ydP9mH4cHl8Hn7hsCBZyI9OdU7SOB7WwGYpbc41doPNhYNRTbnEbF6Gn0MvE+z n4JGFisjyb4= =cYQn -----END PGP MESSAGE----- --==_Exmh_-361153620P-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199901052215.OAA19362>