in reply to Re: Security of Mail Script
in thread Security of Mail Script

It must be secure, unless ofcourse if your database isn't secure (db password must not be readable for users).

The back end of the whole thing is a whole other thing. Our IT people will probably just want to use a .dat file in an obscurely-named folder in /cgi-bin, knowing them. As long as the script doesn't ever give a CGI::Carp type error saying it couldn't find it, that's probably secure enough anyway ... right..?


($_='kkvvttuubbooppuuiiffssqqffssmmiibbddllffss')
=~y~b-v~a-z~s; print

Replies are listed 'Best First'.
Re: Re: Re: Security of Mail Script
by Berik (Sexton) on Feb 09, 2004 at 02:13 UTC
    On public servers, wich I'm dealing with, I can only find one good solution. You should run the script setuid to some user, and let the script then read a datafile with the passord in it. Make sure that user is the only one able to read the password file. Now the location doesn't need to be secure cause the webserver itself or any other user can't read the file. Suggestions welcome for other ways of dealing with this.
    ---
    Berik
[reply]

In Section Seekers of Perl Wisdom