It would seem that you have correctly identified the various pros and cons associated with password storage anytime you must work with a non-interactive environment. The only thought I can offer would be to possibly mitigate the exposure by having secondary accounts on the relevant websites with the minimum access you need to accomplish your goal.

At the very least, be sure than none of the passwords you must use for this are used for any thing else (but I suspect you already follow that practice.) On the plus side, It might be that these can have a high degree of randomness if you never (or rarely) enter them by hand.

The answer to the question "Can we do this?" is always an emphatic "Yes!" Just give me enough time and money.

In reply to Re: Best way to store passwords by boftx
in thread Best way to store passwords by Special_K

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.