Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 7 Apr 2005 14:28:21 -0700
From:      Kris Kennaway <kris@obsecurity.org>
To:        bob@a1poweruser.com
Cc:        Dan Nelson <dnelson@allantgroup.com>
Subject:   Re: nfsiod tasks started in error
Message-ID:  <20050407212821.GA49406@xor.obsecurity.org>
In-Reply-To: <MIEPLLIBMLEEABPDBIEGEELOHDAA.bob@a1poweruser.com>
References:  <20050407204747.GP64927@dan.emsphone.com> <MIEPLLIBMLEEABPDBIEGEELOHDAA.bob@a1poweruser.com>

next in thread | previous in thread | raw e-mail | index | archive | help

[-- Attachment #1 --]
On Thu, Apr 07, 2005 at 05:06:07PM -0400, bob@a1poweruser.com wrote:

> Plan and simple. It's a security hole.

OK, you've changed your mind; last time you were claiming it was a
waste of resources.

> If no nfs is selected in
> sysinstall then there should not be any nfs stuff started at all.

It's in the default kernel, and killing the kernel nfsiod threads will
not disable NFS support.

If you think NFS support is a security hole, remove it from your
kernel and recompile.

Kris

[-- Attachment #2 --]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (FreeBSD)

iD8DBQFCVaX1Wry0BWjoQKURAgTrAKD4GKgWXJWzG5zTydbz3VAdbdh30gCg+6n7
vZrGXIDLJpzu6bHaO151Lgo=
=o2Px
-----END PGP SIGNATURE-----

Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050407212821.GA49406>