Re^3: best way to store login information for a perl script?

I disagree. It's an improvement. The executable could be installed in /usr/local/bin or someplace or be a module in a public lib. The only more secure answer is taking a passkey or something against some encryption keys and you have to do that under either SSL or with echo off in the terminal and the whole point of a tool like this is to make it easier, not to make it a functionally identical interface the web UI.

Comment on Re^3: best way to store login information for a perl script?

Replies are listed 'Best First'.
Re^4: best way to store login information for a perl script? by JavaFan (Canon) on Jul 05, 2009 at 23:42 UTC
You know, the OP didn't strike me as someone who was contemplating putting script like that on a box with multiple users. Or even having the authentication to do so. He certainly wasn't asking about a general program (otherwise, he would have realized that hardcoding a single username/password for a global program isn't going to work anyway). My guess is that either 1) he has written a script which runs from this personal box noone else has access to (in which, it doesn't really matter where he stores the password), or 2) he has written a script while working on a shared box, and isn't root. In which both the script, and the config file are stored somewhere in or below his homedirectory.	[reply]

Replies are listed 'Best First'.

Re^4: best way to store login information for a perl script?
by JavaFan (Canon) on Jul 05, 2009 at 23:42 UTC

My guess is that either 1) he has written a script which runs from this personal box noone else has access to (in which, it doesn't really matter where he stores the password), or 2) he has written a script while working on a shared box, and isn't root. In which both the script, and the config file are stored somewhere in or below his homedirectory.

[reply]