Re: How about a module for "passwords"?

Generally, I would think it better to use the OS' protection mechanisms for this sort of thing.

Set the file access right for the script such that only members of a given group can execute the program and make authorised users a member of that group. That way authorised users only need to remember their standard login passwerds rather than 1 per task.

Examine what is said, not who speaks.

The 7th Rule of perl club is -- pearl clubs are easily damaged. Use a diamond club instead.

Comment on Re: How about a module for "passwords"?

Replies are listed 'Best First'.
Re: Re: How about a module for "passwords"? by John M. Dlugosz (Monsignor) on Jan 25, 2003 at 04:17 UTC
That makes the entire script sensitive. You have to remember to "sanitise" it before sharing the code. And what about backups or version control copies? I think it's useful to have the sensitive information in a different place, even if OS file protection is protection enough.	[reply]