Nice idea fglock. Your solution will work great from the command line. The only problem I foresee is that you're going to run into trouble if the Perl prog is ran as a cron job. You still have to figure out a way to give gpg the password without anyone seeing what it is. If the password is in the "driver" script or a config file root can still read it. I was thinking you could get around this by using a config MySQL table to store the password. You could query the table from your driver script. Only problem with that is you still need to connect to the DB in the first place and then you run into the problem of hiding that login & password. Bugger.

-- vek --

In reply to Re: Re: "safe" perl cron environment? by vek
in thread "safe" perl cron environment? by jhanna

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.