From owner-freebsd-hackers  Wed Jan 17  2:46:18 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11])
	by hub.freebsd.org (Postfix) with SMTP id CAA4237B400
	for <hackers@FreeBSD.org>; Wed, 17 Jan 2001 02:46:01 -0800 (PST)
Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP
          id <aa30069@salmon>; 17 Jan 2001 10:45:57 +0000 (GMT)
To: Peter Pentchev <roam@orbitel.bg>
Cc: mbac@mmap.nyct.net, hackers@FreeBSD.org
Subject: Re: Permissions on crontab.. 
In-reply-to: Your message of "Wed, 17 Jan 2001 12:37:41 +0200."
             <20010117123740.Q364@ringworld.oblivion.bg> 
X-Request-Do: 
Date: Wed, 17 Jan 2001 10:45:57 +0000
From: David Malone <dwmalone@maths.tcd.ie>
Message-ID:  <200101171045.aa30069@salmon.maths.tcd.ie>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> ..or did you mean some kind of unintended/faulty behavior?  Yes,

I ment unintended.

> running crontab setgid does open a window of opportunity for errors,
> but no more, I think, than running it setuid, as it currently is.

True - but I'd say it provides a false sense of security, which
might be more damaging than the extra security provided against
read-only exploits in crontab.

	David.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message