From owner-cvs-all Tue Nov 27 7:15:24 2001 Delivered-To: cvs-all@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id EA4FF37B405; Tue, 27 Nov 2001 07:15:09 -0800 (PST) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.6/8.11.5) with SMTP id fARFEki11669; Tue, 27 Nov 2001 10:14:47 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Tue, 27 Nov 2001 10:14:46 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: Brian Somers Cc: Gregory Neil Shapiro , Mike Silbersack , cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/etc security In-Reply-To: <200111271234.fARCYNU24829@hak.lan.Awfulhak.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, 27 Nov 2001, Brian Somers wrote: > > silby> Do you want me to commit this, or should I wait until you get a > > silby> chance to test it yourself? > > > > It's tested. > > It doesn't look like it handles > > daily_status_security_output="user1 user2" I wondered about that also, but it looks like we already have some code that doesn't correctly handle that scenario: case "${daily_status_security_output:=root}" in /*) echo " (output logged separately)" sh /etc/security -s $args \ >$daily_status_security_output 2>&1;; *) echo " (output mailed separately)" sh /etc/security $args 2>&1 | sendmail $daily_status_security_output;; esac;; Semantics involving multiple mail destinations make sense, but not for files, so if we tweak the := above, it might be possible to make it all make sense. Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message