From owner-freebsd-ports@FreeBSD.ORG Sun May 19 20:59:16 2013 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id D9982BEF for ; Sun, 19 May 2013 20:59:16 +0000 (UTC) (envelope-from ljboiler@gmail.com) Received: from mail-ia0-x22f.google.com (mail-ia0-x22f.google.com [IPv6:2607:f8b0:4001:c02::22f]) by mx1.freebsd.org (Postfix) with ESMTP id A74739E1 for ; Sun, 19 May 2013 20:59:16 +0000 (UTC) Received: by mail-ia0-f175.google.com with SMTP id m10so6776779iam.20 for ; Sun, 19 May 2013 13:59:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:subject:message-id:references:mime-version :content-type:content-disposition:content-transfer-encoding :in-reply-to:user-agent; bh=LRC/pvcP+IyuSsV7N+2uC6MhZwPqd10NUrONq9FAIWc=; b=YfBI7g1kX0iHqcfLJDcklKLs6aQmAexpNMUjCiwbu9JEMVRsDfJsALnrvX4ymlKq6M sgNm4kdnwhVi+0xcrve2l0KxnlKmJqOap2jGvK9jVpdElbE3CgWhZJEGmasrRU0+H567 FJXGFehPxj+9k1LxqsHAQSg3Z1MQWkqq1UeNaWviihnejhPOkP2AnANaXEpsjG785Hm2 erz6S23ZjoPLy7zr+5KJ3W/OQROzwpyR61u9bUfBIxhJkZJ03woVzG7Njt1aXLqiFtXV 088s/zz0EQeXQJJR0f1e0xAV4DG5cNEb1GjNqiVPFor6EMNXwbY21ZTO1O+43gN57F7B qYmA== X-Received: by 10.50.107.106 with SMTP id hb10mr3720756igb.25.1368997156373; Sun, 19 May 2013 13:59:16 -0700 (PDT) Received: from jmobile.jimmy.local (71-81-196-43.dhcp.stls.mo.charter.com. [71.81.196.43]) by mx.google.com with ESMTPSA id d9sm8441316igr.4.2013.05.19.13.59.13 for (version=TLSv1.2 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 19 May 2013 13:59:15 -0700 (PDT) Received: by jmobile.jimmy.local (sSMTP sendmail emulation); Sun, 19 May 2013 15:59:12 -0500 Date: Sun, 19 May 2013 15:59:12 -0500 From: Jimmy To: freebsd-ports@freebsd.org Subject: Re: Why does Samba requires 777 permissions on /tmp Message-ID: <20130519204753.GA47341@jmobile.jimmy.net> References: <20130519115232.49f52d01@scorpio> <20130519195639.79464471@raksha.tavi.co.uk> <20130519151706.4d67afe5@scorpio> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 May 2013 20:59:16 -0000 >From the original post that started this thread, I noticed that the error from portupgrade/ruby was showing the permissions that it didn't like as mode 040777 (octal). This is definitely with the sticky bit turned OFF. It should be 041777. 'stat -r /tmp' will print the permissions in octal rather than the '..rwx...' from ls -l; the permissions is the third group of numbers. Jimmy On Sun, May 19, 2013 at 03:12:08PM -0500, sindrome wrote: > Jerry is right. I have it set to 1777 too and still receive the error > > > On Sun, May 19, 2013 at 2:17 PM, Jerry wrote: > > > On Sun, 19 May 2013 19:56:39 +0100 > > Bob Eager articulated: > > > > > On Sun, 19 May 2013 13:34:49 -0500 > > > sindrome wrote: > > > > > > > I'm not sure I understand your question. Portupgrade barks about > > > > the /tmp directory being world writable. I pasted the exact errors > > > > earlier in this thread. I looked in my path and can't find /tmp in > > > > there and can't figure how to get rid of ruby complaining unless I > > > > remove the writable permissions. When I do that my windows desktop > > > > can't authenticate to my samba server. There has to be a root of > > > > this problem to make them both work. Is there some other place > > > > portupgrade is having /tmp amended on without it being in my $PATH? > > > > > > I went back and had a closer look at your error message. What I hadn't > > > done (and neither had you, prior to that) was read and fully digest > > > the error message. > > > > > > portupgrade is calling its 'system()' function to run a command. The > > > Ruby runtime does a sanity check to make sure that the directories in > > > the path are secure...and /tmp isn't. I suspect that portupgrade puts > > > temporary scripts into /tmp, then executes them; this implies that > > > it's probably chdir'ing to /tmp, then haveing '.' in thge path, or > > > even just adding /tmp to the path, although I don't think so. > > > > > > Anyway, what's insecure is that you don't have the sticky bit set. If > > > you use: > > > > > > chmod 1777 /tmp > > > > > > it ought to all work. > > > > I have the directory chmod set to "1777" and I still receive the error. > > It has been set at that for over two years. This problem only started > > after a "portupgrade" several months ago. > > > > -- > > Jerry ♔ > > > > Disclaimer: off-list followups get on-list replies or get ignored. > > Please do not ignore the Reply-To header. > > __________________________________________________________________ > > > > _______________________________________________ > > freebsd-ports@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" > > > _______________________________________________ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" >