Date: Thu, 10 Jun 1999 17:01:51 -0700 From: Bill Swingle <unfurl@dub.net> To: Nick Rogness <nick@rapidnet.com> Cc: Gregory Carvalho <GregoryC@stcinc.com>, "freebsd-security@FreeBSD.ORG" <freebsd-security@FreeBSD.ORG> Subject: Re: ports and applications Message-ID: <19990610170151.D843@dub.net> In-Reply-To: <Pine.BSF.4.05.9906101501260.33002-100000@rapidnet.com>; from Nick Rogness on Thu, Jun 10, 1999 at 03:07:39PM -0600 References: <375F7453.77C0F526@stcinc.com> <Pine.BSF.4.05.9906101501260.33002-100000@rapidnet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jun 10, 1999 at 03:07:39PM -0600, Nick Rogness wrote: > On Thu, 10 Jun 1999, Gregory Carvalho wrote: > > > Using ipfw I am allowing port 80 through the wall (could you imagine if > > I denied the good people of Gotham their web fix). Suppose I deny > > telnet, but some external server has its telnet server configured for > > port 80. Is there a method to prevent the telnet session from operating? > > Why would anyone run telnet on port 80? > > Is this an incoming or outgoing telnet session? I'm assuming > outoing telnet sessions. The only thing I can think of is running > the machines through a proxy server. Once, while working for a rather fascist employer that denied outgoing connections on ports 22/23 I set up telnet, then later sshd, on port 80 on my home machine. They employers couldnt do without their web access it seems :) I think this is what the original writer is trying to avoid. :) -Bill -- -=| Bill Swingle - unfurl@dub.net - unfurl@freebsd.org - bill@cdrom.com -=| "Computers are useless. They can only give you answers" Pablo Picasso 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?19990610170151.D843>