From owner-freebsd-stable Tue May 29 15:11:58 2001 Delivered-To: freebsd-stable@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id 8419D37B422 for ; Tue, 29 May 2001 15:11:53 -0700 (PDT) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.3/8.11.2) id f4TMBpB30316; Tue, 29 May 2001 15:11:51 -0700 (PDT) (envelope-from dillon) Date: Tue, 29 May 2001 15:11:51 -0700 (PDT) From: Matt Dillon Message-Id: <200105292211.f4TMBpB30316@earth.backplane.com> To: Vivek Khera Cc: stable@FreeBSD.ORG Subject: Re: adding "noschg" to ssh and friends References: <15124.4635.887375.682204@onceler.kciLink.com> <20010529145609.A1209@xor.obsecurity.org> <15124.7132.963202.560009@onceler.kciLink.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :>> marked, and it just seems to follow to me that ssh related binaries :>> should as well. : :KK> No; schg isn't a security feature, at best it's an anti-foot-shooting :KK> feature to prevent accidental trashing of the file. : :I disagree. If my machine is at securelevel > 0, schg is a damned :fine security mesasure to protect sensitive programs from being :trojaned. There's just no way around it short of having access to the :console. I have to disagree with your disagreement. Short of making every single program and configuration file in the entire system schg, all that happens is that the hacker trojans your machine some other (and possibly less detectable) way. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message