i don't see any gaping holes. but i suspect that it's overkill. why not just take advantage of unix groups and permissions? it shouldn't be too hard to set things up so that the webserver and you can read the code but they can't. much less complicated, less of a potential performance hit, and it makes it easier for you to still have access to and modify those scripts if necessary.

what would be really nice would be Access Control Lists. if you're using linux there's a kernel patch that will give you ACLs.

anders pearson

In reply to Re: Apache's mod_perl + (gnuPG + startup.pl) = encrypted code? by thraxil
in thread Apache's mod_perl + (gnuPG + startup.pl) = encrypted code? by one4k4

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.