[11304] in bugtraq
Re: Cisco 675 password nonsense
daemon@ATHENA.MIT.EDU (Brian Elfert)
Sat Aug 7 02:39:48 1999
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Message-Id: <Pine.GSO.3.96.990806133132.18512A-100000@citycenter>
Date: Fri, 6 Aug 1999 13:33:53 -0500
Reply-To: Brian Elfert <brian@CITILINK.COM>
From: Brian Elfert <brian@CITILINK.COM>
X-To: bugtraq@securityfocus.com
To: BUGTRAQ@SECURITYFOCUS.COM
In-Reply-To: <Pine.GUL.4.10.9908061106590.14957-100000@red7.cac.washington.edu>
On Fri, 6 Aug 1999, Dave Dittrich wrote:
> > With good reason. In bridging mode with a Windows 9x/NT box, your network
> > neighborhood will show everyone else's PC that has any file/print sharing
> > enabled. So, it's trivially easy to connect to a non-passworded share.
>
> That depends on the DSL provider, I believe. On my USWest.net DSL
> connection, I only see packets on my side of the bridge that are
> destined for IP addresses I'm using, or broadcast ethernet/IP packets,
> which seems to be the same as what @Home customers (at least the ones
> in Seattle I've spoken with) see. I've heard from other DSL customers
The broadcast packets are what are used for discovering other computers in
the Network Neighborhood.
US West may be filtering on port 139 to prevent this now. This was a
problem with USWest.net, at least in the beginning of DSL.
Brian
