From owner-freebsd-hackers Fri Jan 19 10:38:55 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from orthanc.ab.ca (207-167-15-66.dsl.worldgate.ca [207.167.15.66]) by hub.freebsd.org (Postfix) with ESMTP id 4310E37B402 for ; Fri, 19 Jan 2001 10:38:38 -0800 (PST) Received: from orthanc.ab.ca (localhost [127.0.0.1]) by orthanc.ab.ca (8.11.1/8.11.1) with ESMTP id f0JIbex65641; Fri, 19 Jan 2001 11:37:41 -0700 (MST) (envelope-from lyndon@orthanc.ab.ca) Message-Id: <200101191837.f0JIbex65641@orthanc.ab.ca> To: mbac@mmap.nyct.net (Michael Bacarella) Cc: void , David Malone , Peter Pentchev , hackers@FreeBSD.ORG Subject: Re: Permissions on crontab.. In-reply-to: Your message of "Wed, 17 Jan 2001 20:43:00 EST." <20010117204300.A32417@mmap.nyct.net> Date: Fri, 19 Jan 2001 11:37:40 -0700 From: Lyndon Nerenberg Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "Michael" == Michael Bacarella writes: Michael> Ideally, crontab wouldn't be suid/gid _anything_ and Michael> users own their own crontab file, but perhaps I've said Michael> too much. :) Where, exactly, would you store the users crontab file? It can't go in their home directory. Consider a machine with 10000 accounts, and all the home directories NFS mounted via amd. Imagine what happens the first time cron scans for file modtimes. (Which it has to do unless it has sole control over the users crontab file, which it doesn't in this scenario.) You can't use a 1777 directory, since that lets others DOS your ability to create a crontab (even though the rogue file they dropped in wouldn't be run by a reassonable cron). I like the idea, but please show us a working design. --lyndon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message