On 6/14/12 8:40 AM, jfm wrote: > Hi, > > On 10.6.8, fink was working as expected till yesterday evening. > I then installed fink_0.33.1-51 and passwd_20100706-5. > > > This morning, trying, e.g., to update lame (or transcode, or libxine1), I get > : > >> Setting up fink-buildlock-lame-3.99.5-2 (2012.06.14-16.16.27) ... >> >> sudo -u fink-bld [ENV] sh >> -c/var/folders/EX/EXAfY0MOEsqQGqxa2FaePk+++TI/-Tmp-/fink.lDlPX >> sh: /var/folders/EX/EXAfY0MOEsqQGqxa2FaePk+++TI/-Tmp-/fink.lDlPX: Permission >> denied >> ### execution of >> /var/folders/EX/EXAfY0MOEsqQGqxa2FaePk+++TI/-Tmp-/fink.lDlPX failed, exit >> code 126 > > Note that I have , in fink.conf > RootMethod: none > > The absence of space between the '-c' and the path looked suspicious; > this is easily fixed by adding a space after the -c on line 583 in > %p/lib/perl5/Fink/Services.pm . > But the problem persists after - just eliminates that suspicious absence of > space ; > the msg remains identical, except for that space.. WHAT IS CAUSING the > permissions problem ? > > Permissions are : > # ls -la /var/folders/EX/EXAfY0MOEsqQGqxa2FaePk+++TI > drwx------ 16 jfm staff 544 Jun 14 15:05 -Caches- > drwx------ 10 jfm staff 340 Jun 14 16:16 -Tmp- > drwxr-xr-x 4 jfm staff 136 Jun 11 19:40 . > drwxr-xr-x 3 root wheel 102 May 3 18:08 .. > # ls -l /var/folders/EX/EXAfY0MOEsqQGqxa2FaePk+++TI/-Tmp- > drwx------ 3 jfm staff 102 Jun 13 19:36 Cleanup At Startup > drwx------ 2 jfm staff 68 Jun 13 18:46 PreviewTemp-ZQd7MB > drwx------ 2 jfm staff 68 Jun 13 19:38 PreviewTemp-msT3PP > drwxr-xr-x 2 jfm staff 68 Jun 14 15:05 TemporaryItems > -rwxr-xr-x 1 root staff 207 Jun 14 15:06 fink.IjutN > -rwxr-xr-x 1 root staff 212 Jun 14 15:06 fink.Km9TT > -rwxr-xr-x 1 root staff 214 Jun 14 15:07 fink.eZ8KC > -rwxr-xr-x 1 root staff 207 Jun 14 16:16 fink.lDlPX > > (so, apparently, everybody can read and execute !!!) > > In the corresponding terminal window, I get : > bash-4.2# echo $LOGNAME $USER $HOME > jfm jfm /Users/jfm > bash-4.2# whoami > root > __________________________ > The problem disappears in a window where LOGNAME is unset, > and USER=root , HOME=/var/root, whoami=root. > > > The first type of env is essentially created by, on opening the terminal > window, > exec su -m > ... > exec bash -l > > the second type of environment comes from > exec su - > .... > exec bash -l > > where the files ".profile" in the 2 home-directories are identical, and > source %p/bin/init.sh > > > The first type of way to become root seems at least as good and as honest as > the second, > and I see no reason why the latest version of fink should have problems with > it .. > > > JF Mertens
The issue presumably shows up when you hand control off to the unprivileged 'fink-bld' user via "sudo". I'm curious whether you would see the same thing if you reverted back to fink-0.32.6 and built a package in --build-as-nobody mode. -- Alexander Hansen, Ph.D. Fink User Liaison My package updates: http://finkakh.wordpress.com/ ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Fink-users mailing list [email protected] List archive: http://news.gmane.org/gmane.os.macosx.fink.user Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-users
