[55415] in North American Network Operators' Group
Re: Is it time to block all Microsoft protocols in the core?
daemon@ATHENA.MIT.EDU (Joe Abley)
Tue Jan 28 18:25:48 2003
Date: Wed, 29 Jan 2003 05:07:53 +0545
Cc: Barney Wolff <barney@pit.databus.com>,
Sean Donelan <sean@donelan.com>, nanog@merit.edu
To: "Steven M. Bellovin" <smb@research.att.com>
From: Joe Abley <jabley@isc.org>
In-Reply-To: <20030128231138.9CF447B4D@berkshire.research.att.com>
Errors-To: owner-nanog-outgoing@merit.edu
On Wednesday, Jan 29, 2003, at 04:56 Asia/Katmandu, Steven M. Bellovin
wrote:
> In message <20030128222210.GA84278@pit.databus.com>, Barney Wolff
> writes:
>>
>> On Wed, Jan 29, 2003 at 03:50:34AM +0545, Joe Abley wrote:
>>>
>>> On Wednesday, Jan 29, 2003, at 01:25 Asia/Katmandu, Joe Abley wrote:
>>>
>>>> On FreeBSD, NetBSD, OpenBSD and Darwin/Mac OS X (the only xterms I
>>>> happen to have open right now) this is not the case, and has not
>>>> been
>>>> for some time. I presume, perhaps na?vely, that other operating
>>>> systems have done something similar.
>>>
>>> This is not right. Guess I was typing "man" in the wrong xterms.
>>>
>>> FreeBSD (4.x, 5.x) listens to the network by default (and can be
>>> persuaded not to with a "-s" flag). NetBSD (1.6) does the same.
>>
>> You were right the first time, at least for FreeBSD. The "-s" flag
>> is applied by default - see /etc/defaults/rc.conf . Not quite as
>> idiot-proof as a compiled-in default, but way better than defaulting
>> to listening.
>
> The same is true of NetBSD 1.6; look in the same place.
Serves me right for contradicting myself.
