http://bugzilla.spamassassin.org/show_bug.cgi?id=3623
------- Additional Comments From [EMAIL PROTECTED] 2004-10-02 16:32 ------- Other possibly relevant things. >From perlsec http://www.perldoc.com/perl5.8.0/pod/perlsec.html n recent years, vendors have begun to supply systems free of this inherent security bug. On such systems, when the kernel passes the name of the set-id script to open to the interpreter, rather than using a pathname subject to meddling, it instead passes /dev/fd/3. This is a special file already opened on the script, so that there can be no race condition for evil scripts to exploit. On these systems, Perl should be compiled with -DSETUID_SCRIPTS_ARE_SECURE_NOW. The Configure program that builds Perl tries to figure this out for itself, so you should never have to specify this yourself. Most modern releases of SysVr4 and BSD 4.4 use this approach to avoid the kernel race condition. >From http://www.perldoc.com/perl5.8.0/lib/Pod/Usage.html CAVEATS By default, pod2usage() will use $0 as the path to the pod input file. Unfortunately, not all systems on which Perl runs will set $0 properly (although if $0 isn't found, pod2usage() will search $ENV{PATH} or else the list specified by the -pathlist option). If this is the case for your system, you may need to explicitly specify the path to the pod docs for the invoking script using something similar to the following: pod2usage(-exitval => 2, -input => "/path/to/your/pod/docs"); ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
