From owner-freebsd-security  Mon Jul 31 21:53:10 2000
Delivered-To: freebsd-security@freebsd.org
Received: from silby.com (cb34181-a.mdsn1.wi.home.com [24.14.173.39])
	by hub.freebsd.org (Postfix) with SMTP id 0A64C37BE58
	for <security@freebsd.org>; Mon, 31 Jul 2000 21:53:03 -0700 (PDT)
	(envelope-from silby@silby.com)
Received: (qmail 33807 invoked by uid 1000); 1 Aug 2000 04:52:59 -0000
Received: from localhost (sendmail-bs@127.0.0.1)
  by localhost with SMTP; 1 Aug 2000 04:52:59 -0000
Date: Mon, 31 Jul 2000 23:52:59 -0500 (CDT)
From: Mike Silbersack <silby@silby.com>
To: Greg Hormann <ghormann@alumni.indiana.edu>
Cc: security@freebsd.org
Subject: Re: your mail
In-Reply-To: <Pine.BSF.4.05.10008010024290.89472-100000@hormann.tzo.cc>
Message-ID: <Pine.BSF.4.21.0007312348450.33360-100000@achilles.silby.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-security@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


On Tue, 1 Aug 2000, Greg Hormann wrote:

> Turns out the permit line in my socks5.conf just contained "-", a left
> over from my dialup days.   Not understanding exactly how the SOCKS
> protocol works, I wonder
> 
> (1) What damage might this have done?  The destination port appears to
> always be 6112. Anybody know what is on this port?

That's the port battle.net servers use, but I'm not certain if the address
you listed is one of them or not.

If it is, don't let angry diablo / starcraft fans find you.  (Direct them
to the person relaying through you instead!)

Mike "Silby" Silbersack




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