http://bugzilla.spamassassin.org/show_bug.cgi?id=3586
------- Additional Comments From [EMAIL PROTECTED] 2004-07-12 15:08 -------
Subject: Re: failed sanity check
On Mon, Jul 12, 2004 at 02:44:34PM -0700, [EMAIL PROTECTED] wrote:
> - Solaris, perl version ???: ok
I tried both both 5.005 and 5.8.3
> - MacOS X, perl version ???: fails
5.8.1 RC3
> perl -e 'sub p {print "RUID: $<, EUID: $>\n";} p; use POSIX qw(setreuid);
> POSIX::setreuid(1000,1000); p;'
>
> or setresuid():
>
> perl -e 'sub p {print "RUID: $<, EUID: $>\n";} p; use POSIX qw(setresuid);
> POSIX::setresuid(1000,1000,1000); p;'
>
> however, if those aren't exported, we can't use them :(
That's the case on my Mac OS X box unfortunately:
# perl -e 'sub p {print "RUID: $<, EUID: $>\n";} p; use POSIX qw(setreuid);
POSIX::setreuid(1000,1000); p;'
"setreuid" is not exported by the POSIX module
Can't continue after import errors at
/System/Library/Perl/5.8.1/darwin-thread-multi-2level/POSIX.pm line
19
BEGIN failed--compilation aborted at -e line 1.
# perl -e 'sub p {print "RUID: $<, EUID: $>\n";} p; use POSIX qw(setresuid);
POSIX::setresuid(1000,1000,1000); p;'
"setresuid" is not exported by the POSIX module
Can't continue after import errors at
/System/Library/Perl/5.8.1/darwin-thread-multi-2level/POSIX.pm line
19
BEGIN failed--compilation aborted at -e line 1.
I'm thinking a kluge for this is to simply try it, and instead of
doing a die, throw a debug warning that this is a potential security issue,
and document it somewhere.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
