From owner-freebsd-ports@FreeBSD.ORG Sun May 19 20:12:08 2013 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id CE8631F3 for ; Sun, 19 May 2013 20:12:08 +0000 (UTC) (envelope-from sindrome@gmail.com) Received: from mail-ia0-x234.google.com (mail-ia0-x234.google.com [IPv6:2607:f8b0:4001:c02::234]) by mx1.freebsd.org (Postfix) with ESMTP id A1559865 for ; Sun, 19 May 2013 20:12:08 +0000 (UTC) Received: by mail-ia0-f180.google.com with SMTP id l27so6930478iae.11 for ; Sun, 19 May 2013 13:12:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=3TPXIIBNf3BTDMrkcIApjjbIyyyMeqjwGYl9hZb9Wc8=; b=cK9zT2MUUXZ/h2d7UEZZrar8KSU5bB9MQS5C6+0Hf0ms8jhSuJQBafbAa3AA7/zzzh 015OCNEH8JAqA3C+3ABJ87PQFvcSjB3zIpQjiKZraQl0jwvr/Y5qI/WaS5mrCQXixlf7 iWC5BGfe5A4Il/q7H68A1bQOmWFdXvf4BVnU6ek5UaLVzMHFpckDNfJml/AdhP28g/Yx CgnaSe5oawYWy89W6qbtIEorz2Y061psIUUZvQB6xu16rOmrLMcIr7izDRKKt1BN1VOI Ad4DBnGnVeNyXtnqD+jBr6hvD2WVUPvNwykr8kJhYEQVuxtEBiLiJuYrHNwRLxfdLMOn RIGg== MIME-Version: 1.0 X-Received: by 10.50.33.73 with SMTP id p9mr3426917igi.90.1368994328311; Sun, 19 May 2013 13:12:08 -0700 (PDT) Received: by 10.64.235.172 with HTTP; Sun, 19 May 2013 13:12:08 -0700 (PDT) In-Reply-To: <20130519151706.4d67afe5@scorpio> References: <20130519115232.49f52d01@scorpio> <20130519195639.79464471@raksha.tavi.co.uk> <20130519151706.4d67afe5@scorpio> Date: Sun, 19 May 2013 15:12:08 -0500 Message-ID: Subject: Re: Why does Samba requires 777 permissions on /tmp From: sindrome To: FreeBSD Mailing List Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 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:12:08 -0000 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 =E2=99=94 > > 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" >