[55408] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: Is it time to block all Microsoft protocols in the core?

daemon@ATHENA.MIT.EDU (Joe Abley)
Tue Jan 28 17:10:46 2003

Date: Wed, 29 Jan 2003 03:50:34 +0545
Cc: Sean Donelan <sean@donelan.com>, nanog@merit.edu
To: Joe Abley <jabley@isc.org>
From: Joe Abley <jabley@isc.org>
In-Reply-To: <4F30B1E1-32F8-11D7-9DAE-00039312C852@isc.org>
Errors-To: owner-nanog-outgoing@merit.edu



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=20
> happen to have open right now) this is not the case, and has not been=20=

> for some time. I presume, perhaps na=EFvely, that other operating=20
> 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=20
persuaded not to with a "-s" flag). NetBSD (1.6) does the same.

Darwin/Mac OS X and OpenBSD do not listen by default (and can be=20
persuaded to listen with a "-u" flag). (Looks like Darwin ships with=20
OpenBSD's syslogd).

Various people mailed me and told me that "Linux" does not listen by=20
default, presumably for commonly-packaged values of "Linux".


Joe


home help back first fref pref prev next nref lref last post