From owner-freebsd-security  Mon Mar  5 11:47:33 2001
Delivered-To: freebsd-security@freebsd.org
Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147])
	by hub.freebsd.org (Postfix) with ESMTP id 5144837B718
	for <freebsd-security@FreeBSD.ORG>; Mon,  5 Mar 2001 11:47:30 -0800 (PST)
	(envelope-from phk@critter.freebsd.dk)
Received: from critter (localhost [127.0.0.1])
	by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id f25JllB01868;
	Mon, 5 Mar 2001 20:47:47 +0100 (CET)
	(envelope-from phk@critter.freebsd.dk)
To: David Syphers <dsyphers@hep.uchicago.edu>
Cc: freebsd-security@FreeBSD.ORG
Subject: Re: sshd listening on port 6010 
In-Reply-To: Your message of "Mon, 05 Mar 2001 13:44:22 CST."
             <Pine.SGI.4.33.0103051338440.383702-100000@hep.uchicago.edu> 
Date: Mon, 05 Mar 2001 20:47:47 +0100
Message-ID: <1866.983821667@critter>
From: Poul-Henning Kamp <phk@critter.freebsd.dk>
Sender: owner-freebsd-security@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

In message <Pine.SGI.4.33.0103051338440.383702-100000@hep.uchicago.edu>, David 
Syphers writes:
>Does anyone know why sshd listens on port 6010 when someone is ssh'd into
>a box?

It's called "X11-forwarding"

--
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-security" in the body of the message