From owner-freebsd-ports@FreeBSD.ORG  Mon May 20 13:03:09 2013
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
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 B0154876
 for <freebsd-ports@freebsd.org>; Mon, 20 May 2013 13:03:09 +0000 (UTC)
 (envelope-from sindrome@gmail.com)
Received: from mail-ie0-x22c.google.com (mail-ie0-x22c.google.com
 [IPv6:2607:f8b0:4001:c03::22c])
 by mx1.freebsd.org (Postfix) with ESMTP id 86CD179F
 for <freebsd-ports@freebsd.org>; Mon, 20 May 2013 13:03:09 +0000 (UTC)
Received: by mail-ie0-f172.google.com with SMTP id 16so13935102iea.3
 for <freebsd-ports@freebsd.org>; Mon, 20 May 2013 06:03:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:x-received:in-reply-to:references:date:message-id
 :subject:from:to:content-type;
 bh=fiHrVJWi9bzGwsnIkFcgj+wQTktgIiB310WUkHU2IBA=;
 b=nCadScTZ0K3DHICH6NTC66FlZTsCu0kJrvZnprhS5QX0K2LCjuaJS4oP9eIW0iAsHL
 IpKuaKWeTzi2U7Z4DCL0dmv2ZJg2BnNOPQAHGssS4MtjtIsiMevvNo4aq3yXaunMeqaT
 JPMtp0Cb1eZ451DuxMPfZHzF9zdn3+14DuBTOm8YooAVirZeAIH4nvNB1L+SJN61t/Ib
 gnhIyz7VecKbxkQV3tm5HKKvbXBAtVpA2Dnwy7z15yD61sIph2Z7uOvIEnF+rUjqG8eN
 9p8NTcWkejaMCzjhuulIy/+i9amEv6eX+LH5gL2Wj8wfD+FQ+B+KkL3AikiWFIxA37tL
 Jjgw==
MIME-Version: 1.0
X-Received: by 10.42.196.138 with SMTP id eg10mr32059065icb.5.1369054989231;
 Mon, 20 May 2013 06:03:09 -0700 (PDT)
Received: by 10.64.235.172 with HTTP; Mon, 20 May 2013 06:03:09 -0700 (PDT)
In-Reply-To: <8661yedqyy.wl%poyopoyo@puripuri.plala.or.jp>
References: <CAFzAeSdgRotc34+eyfVHZBA-QGUCWJ1MZDYw1ysRxEV9MhG2BQ@mail.gmail.com>
 <8661yedqyy.wl%poyopoyo@puripuri.plala.or.jp>
Date: Mon, 20 May 2013 08:03:09 -0500
Message-ID: <CAFzAeSe4YTdUiqcxSDUGDf6fQEeDK_sDVYym1hsck8fms8kJqA@mail.gmail.com>
Subject: Re: Why does Samba requires 777 permissions on /tmp
From: sindrome <sindrome@gmail.com>
To: sindrome <sindrome@gmail.com>,
 FreeBSD Mailing List <freebsd-ports@freebsd.org>, 
 poyopoyo@puripuri.plala.or.jp
Content-Type: text/plain; charset=ISO-8859-1
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 <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 20 May 2013 13:03:09 -0000

Looks like a step in the right direction.  How do I troubleshoot to figure
out what application is appending/changing the value of PATH?


On Mon, May 20, 2013 at 2:56 AM, <poyopoyo@puripuri.plala.or.jp> wrote:

> At Sat, 18 May 2013 18:34:47 -0500,
> sindrome wrote:
> > /usr/local/lib/ruby/site_ruby/1.8/pkgtools/pkgtools.rb:483: warning:
> > Insecure world writable dir /tmp in PATH, mode 040777
>
> At Sun, 19 May 2013 23:31:21 -0500,
> sindrome wrote:
> > /usr/local/lib/ruby/site_ruby/1.8/pkgtools/pkgtools.rb:483: warning:
> > Insecure world writable dir /tmp/. in PATH, mode 041777
>
> At Sun, 19 May 2013 21:30:03 +0200,
> Simon Wright wrote:
> > /usr/local/lib/ruby/site_ruby/1.8/pkgtools/pkgtools.rb:288: warning:
> > Insecure world writable dir /tmp/ in PATH, mode 041777
>
> /tmp
> /tmp/.
> /tmp/
>
> Interesting three different messages.
> It looks like three different entities adds their own value to your PATH.
>
> What you guys should do first is to find who sets stupid PATH for you.
> I don't suppose portupgrade does.
>