Careful! Leaving something as obvious as $ENV{'PATH'} unset where your program relies on it is a blatant security hole. Anyone could set this beforehand to execute arbitrary code from a setuid root script! The best solution is to hard code the path right in to prevent any further complication. '/usr/bin/cat' instead of 'cat', for example. I hope you are also enabling taint checking for this CGI script! If you use any form-inputted data to run your program, the program will fail, as it should since an executed program could have some lethal or illegal or hacker arguments which perl would not be able to catch. The best solution is to use a CPAN module, but if that doesn't exist, then running executables from a CGI is generally very dangerous- every CGI execution will now consist of 2 processes- twice as many (not considering any prebuffering or other CGI speederuppers). It's best to avoid it, but if you can't, then closely monitor the the path to the binary as well as any arguments it may take.
AgentM Systems nor Nasca Enterprises nor Bone::Easy nor Macperl is responsible for the comments made by AgentM. Remember, you can build any logical system with NOR.

In reply to Re: Environment Paths by AgentM
in thread Environment Paths by otijim

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.