Comment on

ptkdb covers the SSH side of things well.

As for any database passwords, I'd be inclined to simply store passwords in a file that is readable only by the user running the script.
Parse, do or otherwise include that file as required.

If that requires a new user and/or group just for running automated commands, so be it.

Cheers,

BazB

If the information in this post is inaccurate, or just plain wrong, don't just downvote - please post explaining what's wrong.
That way everyone learns.

In reply to Re: plaintext password in scripts run through cron by BazB
in thread plaintext password in scripts run through cron by krusty

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

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, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

Outside of code tags, you may need to use entities for some characters:

	For:		Use:
	&		`&`
	<		`<`
	>		`>`
	[		`[`
	]		`]`

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.


good chemistry is complicated, and a little bit messy -LW
	PerlMonks

Comment on

How many continents have you visited?