From owner-freebsd-security Mon Jul 15 14:49:51 1996 Return-Path: owner-security Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA19440 for security-outgoing; Mon, 15 Jul 1996 14:49:51 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA19427 for ; Mon, 15 Jul 1996 14:49:46 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id PAA21014; Mon, 15 Jul 1996 15:49:31 -0600 (MDT) Date: Mon, 15 Jul 1996 15:49:31 -0600 (MDT) Message-Id: <199607152149.PAA21014@rocky.mt.sri.com> From: Nate Williams To: e8917523@antares.linf.unb.br (Daniel C. Sobral) Cc: security@freefall.freebsd.org Subject: Re: Specific problem??? In-Reply-To: <9607152212.AA15879@antares.linf.unb.br> References: <199607152043.NAA09614@freefall.freebsd.org> <9607152212.AA15879@antares.linf.unb.br> Sender: owner-security@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Please stop sending your local information to freebsd-security! It > > is not a forum to discuss your specific system's security problems. > > ??? I was given the impression that the problem was present, for instance, > in all FreeBSD 2.1.0-R, and possibly the newly released 2.1.5-R. How does > that constitue a "specific system's security problem"? First of all, 2.1.5 doesn't have the problem. Second of all, I think the complaint was that they were asking for advice on 'local' adminstration issues such as what files to remove suid on, etc.. The administrator shows a lack of knowledge on Unix security, and reading a good security book would be better use of both their time and ours. Nate