Date: Wed, 12 Mar 1997 10:25:11 -0500 From: Garrett Wollman <wollman@lcs.mit.edu> To: Guido van Rooij <guido@gvr.win.tue.nl> Cc: freebsd-security@freebsd.org, core@freebsd.org Subject: Re: NFS security issue... Message-ID: <9703121525.AA18864@halloran-eldar.lcs.mit.edu> In-Reply-To: <199703121303.OAA19396@gvr.win.tue.nl> References: <19970312011954.205.qmail@char-star.rdist.org> <199703121303.OAA19396@gvr.win.tue.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
<<On Wed, 12 Mar 1997 14:03:00 +0100 (MET), Guido van Rooij <guido@gvr.win.tue.nl> said: >> Once we know how to do that, the change to sys/nfs/nfs_socket.c to check >> privileged ports if "net.inet.nfs.secure" is on is trivial, and can be >> committed and tested immediately. >> > Well it is really straightforwrad to do. In fact I had it lying around. Except, of course, that it doesn't belong under net, it belongs under [v]fs.nfs. At this point, you may want to fix P-HK's breakage of sysctl variables for LKM filesystems. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, ANA, or NSA| - Susan Aglukark and Chad Irschick
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9703121525.AA18864>