Read perlsec. Secure setuid scripts means the kernel invokes the setuid interpreter for the script with a filehandle to that script opened. It affects perl in its way to handle setuid scripts: read it from the special file descriptor, or complain. For more info on the underlying problem see also the hacking FAQ, question 8. Linux does not have secure setuid scripts; that kernel ignores the setuid bit on scripts.What does this mean? How do I discover if my OS supports these? How does this setting affect the resulting Perl?
- ``Does your kernel have *secure* setuid scripts? [n]''
--shmem
_($_=" "x(1<<5)."?\n".q·/)Oo. G°\ /
/\_¯/(q /
---------------------------- \__(m.====·.(_("always off the crowd"))."·
");sub _{s./.($e="'Itrs `mnsgdq Gdbj O`qkdq")=~y/"-y/#-z/;$e.e && print}
In reply to Re: building Perl: a few Configure questions
by shmem
in thread building Perl: a few Configure questions
by j3
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |