From owner-freebsd-hackers Mon Jun 8 11:13:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA08557 for freebsd-hackers-outgoing; Mon, 8 Jun 1998 11:13:25 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.numachi.com (numachi.numachi.com [198.175.254.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA08485 for ; Mon, 8 Jun 1998 11:13:05 -0700 (PDT) (envelope-from reichert@numachi.numachi.COM) Received: (qmail 5656 invoked by uid 1001); 8 Jun 1998 18:12:58 -0000 Message-ID: <19980608141258.A5542@numachi.com> Date: Mon, 8 Jun 1998 14:12:58 -0400 From: Brian Reichert To: hackers@FreeBSD.ORG Subject: _secure_path and cron Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hiya- ( This is with 2.2.6-RELEASE, BTW. ) I was playing with setting up some really strict permissions on user accounts: > groups breicher breicher wheel users > ls -ld ~breicher drwxrws--T 11 root breicher 1024 Jun 8 13:52 /home/breicher/ Note that I'm in my own group, but root owns the directory, granting group access. Files in the directory are owned by the user. I'll spare the details of why I was persuing this. I began to note cron barfing: Jun 8 13:20:00 breichert CRON[12376]: _secure_path: cannot stat /home/breicher/ .login_conf: Permission denied The file in question does not exist, therefore _secure_path should have returned -2, which does not warrent logging via syslog. I presume that _secure_path instead returned -1, which confuses me. If cron, at that point, was running as either root, or me, there should be no permission errors. Is this a bug, or am I being too clever for my own good? What gives? -- Brian Reichert reichert@numachi.com 37 Crystal Ave. #303 Current daytime number: (617)-873-4337 Derry NH 03038-1713 USA Intel architecture: the left-hand path To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message