Re: Some perl team statistics
Stefan Hornburg (Racke) wrote:
> On 11/26/2010 10:28 AM, Christian Kuelker wrote:
>> 1) add a config file to the script. Use some simple and human
>> readable format. Config::Tiny will do.
>> The motivation is. if you make the configuration of the database (
>> user name and password) external, you can not make the mistake to
>> upload any password to the SVN.
>> So having to deal with a password in a script should only be done
>> via: a) cfg file or b) command line option. But not saved in a script.
> b) is bad as everyone else on the system can grab the password.
> So either a) or c) password by prompt or d) .my.cnf or similar file for
I would d) be considered included in a) because d) is just fixed
location for a config file, while a) was not suggesting a certain
Also I would be consider b) as better then z) "save password in
file". The quality of better is in regard of the time of permanent
visibility of the password. z) is stored forever and might be seen
by others, where b) is not stored. But of course I would not see b)
as a good option in general, because - you are right - it can be
seen by others easily if not used in a wrapper. c) is of course
better then b). And a) is the best solution.