From: SMTP%"hobbit@avian.org" 26-SEP-1996 19:11:15.23 To: EVERHART CC: Subj: BoS: NT security et al Resent-Date: Thu, 26 Sep 1996 19:25:14 +1000 Approved-By: ALEPH1@UNDERGROUND.ORG Approved-By: *Hobbit* Message-ID: <199609251706.NAA05221@work.avian.org> Date: Wed, 25 Sep 1996 13:06:57 -0400 Reply-To: *Hobbit* Sender: Bugtraq List From: *Hobbit* To: Multiple recipients of list BUGTRAQ Approved: proff@suburbia.net Resent-Message-ID: <"xG0SJ3.0.Zr5.vlaIo"@suburbia> Resent-From: best-of-security@suburbia.net X-Mailing-List: archive/latest/415 X-Loop: best-of-security@suburbia.net Precedence: list Resent-Sender: best-of-security-request@suburbia.net Subject: BoS: NT security et al I've been screwing around some with netbios in general, and being more or less horrified [but not surprised, this is microsnot after all]. I've learned that one hack you can do in the absence of any other overall defenses is to use a non-null SCOPE ID. They don't recommend it but that's probably just because of the potential administrative headaches in manually changing the scope on every machine in a facility. The scope ID would be sort of a "global password" to your netbios service, sort of the same way as YP domains, so it needs to be nonobvious and kept within your walls. Better than nothing, though... Unfortunately the right place to set it seems to be buried under obscure and ill-named menu items that vary from platform, so you'll have to hunt around. _H*