ASPN ActiveState Programmer Network
ActiveState
/ Home / Perl / PHP / Python / Tcl / XSLT /
/ Safari / My ASPN /
Cookbooks | Documentation | Mailing Lists | Modules | News Feeds | Products | User Groups


Recent Messages
List Archives
About the List
List Leaders
Subscription Options

View Subscriptions
Help

View by Topic
ActiveState
.NET Framework
Open Source
Perl
PHP
Python
Tcl
Web Services
XML & XSLT

View by Category
Database
General
SOAP
System Administration
Tools
User Interfaces
Web Programming
XML Programming


MyASPN >> Mail Archive >> perlex
perlex
Re: Calling SOAP::Lite with CommandLineOptions=-T (taint-checking)
by Richard A. Wells other posts by this author
Jul 11 2005 10:26AM messages near this date
Calling SOAP::Lite with CommandLineOptions=-T (taint-checking) | Re: Calling SOAP::Lite with CommandLineOptions=-T (taint-checking)
SERVICES Following up to my earlier as-yet-unanswered question about 
Taint-checking failing with SOAP::Lite:

I found this post by Stas Bekman:

    http://groups-beta.google.com/group/perl.perl5.porters/browse_thread/thread/501ef4ea5128
118c/79773a3a74856cf6?q=%22Insecure+dependency+in+require+while+running+with+-T+switch%22&rn
um=1&hl=en#79773a3a74856cf6

which led me to add the following to my script:

    BEGIN {
         @INC = ('c:\perl\lib', 'c:\perl\site\lib');
         $ENV{PATH} = 'c:\perl\bin';
    }

in hopes that Stas's point (that it isn't really the module but a 
tainted value in @INC or $ENV{PATH} that is causing the problem) is 
correct.  Unfortunately, it doesn't fix the problem.

Another clue is that somehow the PerlEx precompiler is involved. Here's 
the PerlEx log file fragment:

    *** 'd:\bco\plex\bcoqt' log message at: 2005/07/11 13:12:25
    Precompiler: Execute Error:
        Filename:[d:\bco\plex\bcoqt]
        Package:[PerlEx::Precompiler::d_::bco::plex::bcoqt]
    Params[]
    Insecure dependency in require while running with -T switch at
    d:/perl/site/lib/SOAP/Lite.pm line 1510.
    BEGIN failed--compilation aborted.

Any other suggestions for how to debug, fix, or workaround this 
problem?  It's a showstopper for the next version of a system that's 
been running happily on PerlEx for a couple of years now but now needs 
to make SOAP calls.

Cheers,
Richard

-- 
*** Richard A. Wells, raw@[...].com, +1.978.371.7425
*** Reality And Wonder, http://www.raw.com/
Attachments:
unknown1
unknown2
unknown3
unknown4

Thread:
Richard A. Wells
Richard A. Wells
Nick ***
Richard A. Wells
Richard A. Wells

Privacy Policy | Email Opt-out | Feedback | Syndication
© 2004 ActiveState, a division of Sophos All rights reserved