The question is about DBI, and having passwords in the script. It seems a bit of a problem for bigger systems. If you have a perl system script and want to allow users to use it, they need read priviledges, which allows them to see the password, yes?
Someone mentioned the DBIx modules, which almost do what you want, but not really, since they don't prevent other users from using your virtual user in the same way, and still having access to the database.
So I am wondering if we perl monks in all our glorious perl
light can come up with something (other than suid wrappers for
the perl script, which would work... but is overkill and
possibly a security hole) to fix this. I thought of a system
to request the password from another program, based on the script
location... I.E. /usr/bin/foo may access this password, but no
one else... unfortunately, I can't seem to find a foolproof
way for verifying the name of a script.
Does anyone else have ideas? It seems like a valid project,
and if it could be implemented right, it could have uses
in other places as well...
Of course, I may also be missing some fundamentally simple
solution, too, but I'll never know until I ask, will I?
TIA - Ant
In reply to Hiding passwords in scripts... by suaveant
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |