Date: Thu, 3 Jul 2003 15:04:52 -0700 From: Matthew Hunt <mph@astro.caltech.edu> To: K Anderson <freebsduser@comcast.net> Cc: freebsd-questions@freebsd.org Subject: Re: Disable PING command Message-ID: <20030703220452.GA25156@wopr.caltech.edu> In-Reply-To: <3F04A7EE.5070701@comcast.net> References: <Law11-F108KHs7c6NdD00055715@hotmail.com> <3F049A3D.3040104@comcast.net> <20030703215110.GA24901@wopr.caltech.edu> <3F04A7EE.5070701@comcast.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jul 03, 2003 at 03:02:22PM -0700, K Anderson wrote: > Well, all I have to do then as a user who can't run ping is get it from > someplace else and just do ./ping in my home directory. Correct? Or even > use a perl script to do it. If that's possible. No. Normal users can't create the raw sockets that ping needs to work. A ping executable, no matter where it came from, is not going to work unless it's suid root (or run by root). Normal users obviously cannot mark an executable suid root. > The above example then becomes pointless and the poster did ask to > disable it or get rid of it all together. Just shutting down the > /sbin/ping isn't enough. That's all I am saying. :) You're wrong. You would be right if we were talking about lots of other programs, but not ping. -- Matthew Hunt <mph@astro.caltech.edu> * Science rules. http://www.pobox.com/~mph/ *
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030703220452.GA25156>