oracle - Best practices for holding passwords in shell / Perl scripts? -
i've had dust off perl , shell script skills out colleagues. colleagues in question have been tasked providing reports internal application large oracle database backend, , don't have skills this. while might question whether have skills either (grin), apparently enough people think mean can't weasel out of it.
so question - in order extract reports database, script having connect , run queries. haven't far managed come solution store username , password database being stored plaintext in script.
is there solution else has written, perhaps cpan module? or there else that's better - keep user / password combo in separate file that's hidden away somewhere else on filesystem? or should keeping them trivially encrypted avoid them being pulled out of scripts system-wide grep?
edit: oracle database sits on hp-ux server.
application server (running shell scripts) solaris.
setting scripts owned me no-go, have owned service account multiple support personnel have access to.
scripts intended run cron jobs.
i'd love go public-key authentication, unaware of methods make work oracle - if there such method - enlighten me!
best practice, imho, not hold passwords in shell / perl script. public key authentication for.
Comments
Post a Comment