in reply to Apache's mod_perl + (gnuPG + startup.pl) = encrypted code?

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

  • Comment on Re: Apache's mod_perl + (gnuPG + startup.pl) = encrypted code?

Replies are listed 'Best First'.
Re: Re: Apache's mod_perl + (gnuPG + startup.pl) = encrypted code?
by one4k4 (Hermit) on May 30, 2002 at 15:55 UTC
    Nice point. I hadn't thought about that fact that perl scripts are frequently changed. And a good reason to use perl is the fact that you don't have to do anything after you make the script.. User permissions would be a good idea, but you know, the geek in me ran with it. ;)

    _14k4 - perlmonks@poorheart.com (www.poorheart.com)