comment on

The most important consideration may be, what do the auditors accept?

Auditors do not like text files. Period.

Auditors are mostly ok with public/private key pairs.
They don't seem to mind Oracle's wallet.
Key stores seem to be a mixed bag.

As an Oracle DBA, and familiar with the wallet, it makes no sense to me that Oracle wallet is ok, but a read only text file is not. A hacker needs to crack Oracle to get access to the config file, and once they're Oracle, the wallet is theirs to toy with. As is the database ... as are the private keys ... that text file is the least of your problems ...

Whatever you do, don't let the auditors, or the people in your organization who's only job is to handle the auditors, know that you're pondering security considerations, lest every decision you make for the next four years gets forwarded to committee for review. You'll have to quit your job in order to even think about doing another honest day's work ever again. Ever. Like Ever. </rant> Oops, I forgot my opening rant tag. (And apologies to Taylor Swift)

Thanks,
cbeckley

In reply to Re: Accessing passwords in a script by cbeckley
in thread Accessing passwords in a script by nysus

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Think about Loose Coupling
	PerlMonks