Sorry :) /etc/sysconfig/msec says: UMASK_ROOT=022 SECURE_LEVEL=4 HISTFILESIZE=10 UMASK_USER=022 TMOUT=0
I tried running msec but no matter which level I set it to, it still doesn't seem to affect the perl behavior. Whatever level I set does show in /etc/sysconfig/msec. Ryan > On Mon, 2003-07-28 at 13:30, Ryan Hanlon wrote: >> Here's the /etc/security/msec directory: >> >> -rwxr-xr-x 1 root root Jul 10 11:47 security.conf* >> lrwxrwxrwx 1 root root 27 Jul 10 11:05 server -> >> /etc/security/msec/server.4 >> -rw-r--r-- 1 root root 193 Mar 7 06:41 server.4 >> -rw-r--r-- 1 root root 104 Mar 7 06:41 server.5 >> > > that's very nice, now cat /etc/sysconfig/msec like I said :-) That's > where you'll see the level that's being set. > >> And env says SECURE_LEVEL=4. From that directory though, I can't see >> the >> correct way to set it lower than 4. I don't think you can just change >> the >> variable (I can 'export SECURE_LEVEL=1', but it doesn't change the perl >> behavior). >> >> Ryan >> > > man msec -- you can msec [level] to change it. > >> >> On 28 Jul 2003, Jack Coates wrote: >> >> > Funky. What's the msec SECURE_LEVEL? cat /etc/sysconfig/msec. If it's >> 4 >> > or 5, that's a damn good place to start looking. >> > >> > On Mon, 2003-07-28 at 12:14, Ryan Hanlon wrote: >> > > I installed 9.1 a few weeks ago, and just recently discovered that >> > > non-root users can't run perl scripts. If I run any script with >> > > #!/usr/bin/perl in the first line, I get something like this: >> > > >> > > -bash: ./test.pl: /usr/bin/perl: bad interpreter: Permission denied >> > > >> > > >> > > The script itself is executable, and permissions are correct on >> Perl. >> > > (/usr/bin/perl is a link to perl5, which is a link to 5.8.0, which >> is 755) >> > > >> > > There are no \r's or other odd characters in the shebang line. >> > > >> > > There are no acl's set on any of /usr/bin/perl* or the parent >> directories. >> > > >> > > Any normal user can execute /usr/bin/perl somescript.pl, but can't >> run >> > > somescript.pl by itself. >> > > >> > > >> > > If this is a problem with the default Mandrake setup then I'm sure >> the >> > > question has been asked before, but I haven't found any suggestions >> on >> > > Google except the usual things above. Is there anything else that >> can >> > > cause this? Maybe extra restrictions set in kernel-secure? I can't >> > > imagine why someone would think that's a security feature. And for >> the >> > > bonus question, how can I undo whatever it is that prevents users >> from >> > > running perl normally? >> > > >> > > Appreciate any thoughts. >> > > >> > > Ryan >> > > >> > > >> > > >> > > ______________________________________________________________________ >> > > >> > > Want to buy your Pack or Services from MandrakeSoft? >> > > Go to http://www.mandrakestore.com >> > >> >> >> >> ______________________________________________________________________ >> >> Want to buy your Pack or Services from MandrakeSoft? >> Go to http://www.mandrakestore.com > -- > Jack Coates > Monkeynoodle: A Scientific Venture... > > >
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
