Unless someone posts a better idea, my suggestion would be to pull the critical information out of the script into a configuration file that is read by the script, then set the permissions on the file such that only the user the script is running as can read it (0500 under *nix, for example). You may also wish to store the configuration file in a directory location that is also unavailable to other users.

An alternative might be to encrypt the configuration file, and decrypt it when it is read. This, however, runs into a similar issue as before, with the key having to be accessible to the script, and therefore anyone use who can read it.

Hope that helps, and look forward to seeing the comments and suggestions of others to your query.

---

---

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! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

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:
	&		&
	<		&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.