From owner-freebsd-security Fri Jul 9 16:15:44 1999 Delivered-To: freebsd-security@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 7D816150E2 for ; Fri, 9 Jul 1999 16:15:22 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id RAA06023; Fri, 9 Jul 1999 17:15:21 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id RAA22161; Fri, 9 Jul 1999 17:13:16 -0600 (MDT) Message-Id: <199907092313.RAA22161@harmony.village.org> To: Cliff Skolnick Subject: Re: suid/guid Cc: Dag-Erling Smorgrav , Gustavo V G C Rios , security@FreeBSD.ORG, bos-owner-br@sekure.org In-reply-to: Your message of "Fri, 09 Jul 1999 15:10:39 PDT." References: Date: Fri, 09 Jul 1999 17:13:16 -0600 From: Warner Losh Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message Cliff Skolnick writes: : I have cron jobs that want this info, and I would rather not run my cron : jobs as root. IMHO a few setuid root, or setgid something executables are : way better than setuid root cron scripts. You have cron jobs that do a DF on unmounted file systems? That's the only thing that removing the setgid bit will impact. Generally, only root will want to do this. df on other file systems is unaffected as that information is available to non-priviledged users. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message