Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 17 Jun 2008 16:09:44 +0300
From:      "V.Chukharev" <chukharev@mail.ru>
To:        "Jeremy Messenger" <mezz7@cox.net>
Cc:        gnome@freebsd.org
Subject:   Re: FreeBSD port x11-toolkits/vte makes /usr(local world writable
Message-ID:  <op.ucv9ii2b0g54sc@localhost>
In-Reply-To: <op.uchruimr0g54sc@localhost>
References:  <op.ucfggxwe0g54sc@localhost> <op.ucfrz1yx9aq2h7@mezz.mezzweb.com> <op.uchruimr0g54sc@localhost>

next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 09 Jun 2008 20:21:44 +0300, V.Chukharev <chukharev@mail.ru> wrot=
e:

> On Sun, 08 Jun 2008 18:29:51 +0300, Jeremy Messenger <mezz7@cox.net> w=
rote:
>
>> On Sun, 08 Jun 2008 06:21:07 -0500, V.Chukharev <chukharev@mail.ru> w=
rote:
>>
>>> Hi,
>>>
>>> I have seen the following error a number of times after upgrading th=
e
>>> ports last month or two.
>>> $ portversion -OvL=3D
>>> /usr/local/lib/ruby/site_ruby/1.8/pkgtools.rb:1137: warning: Insecur=
e
>>> world writable dir /usr/local in PATH, mode 040777
>>> /usr/local/lib/ruby/site_ruby/1.8/pkgmisc.rb:136: warning: Insecure
>>> world writable dir /usr/local in PATH, mode 040777
>>>
>>> Indeed, the dir is world writable:
>>> $ ls -ld /usr/local
>>> drwxrwxrwx  27 root  wheel  512  2 Jun 21:57 /usr/local
> [...]
>> I can't reproduce it when I reinstalled vte.
>>
>> # ls -ld /usr/local
>> drwxr-xr-x  16 root  wheel  512 Jun  7 08:42 /usr/local/
>
> Thanks for trying. I guess it's something with my world then. I had pr=
oblems when
> tried to build the world with -Os (which worked for me on 6-STABLE), t=
hen
> I removed it from COPTFLAGS but left in CFLAGS...
>
> I'll make a new world with no optimization and come back again. This m=
ight
> take a while though.

I have rebuilt the world, and then started to rebuild all the installed =
ports,
(anyway, gettext was changed). I rebuilt the ports alphabetically, like
portupgrade -m -DNOCLEANDEPENDS --batch -x openoffice.org  -wkpf '[A-a]*=
'
then 'b*', etc. In between of installations I searched for programs with=

wrong modes. Since approximately middle of tha alphabet (e.i. after 'g*'=
 to 'm*',
I cannot tell more accurately) the wrong modes stopped to appear.

My guess is that one of the ports used to build others had problems, per=
haps
due to optimization flags earlier used via make.conf, or due to upgrade =
with
umask 07. Once I noticed a warning that umask is wrong after a number po=
rts
got upgraded, perhaps I missed some of them with force rebuild with corr=
ected
umask.

Thanks!

>> Cheers,
>> Mezz
>>
>>> Best regards,
>>
>>
>
> Best regards,

-- =

V. Chukharev



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?op.ucv9ii2b0g54sc>