Fellow Monasterians
I've been asking around for the best way to set up a new site securely and gotten lots of conflicting advice (and lots of interpretations of "securely"). Even though I risk flogging a dead horse, I have to ask here at PM's before making any final decisions.
I originally thought that CGIwrap was the way to go, but I'm having problems getting it to work with CGI::Application's instance scripts, e.g.,
use lib "../cgi-bin/cgiwrap/username/"; use warnings; use strict; use CGI::Carp qw(fatalsToBrowser); use DSAdmin;
which finds my module, but won't open a .config file (contains database log-on username and password) in my home directory that is set to 700 (which it is supposed to be able to do as a cgiwrapped script).
Some have suggested placing my Perl in a directory in my home directory, but I end up with the same inability to read that .config file because of permissions.
The other reason I'm considering the home directory route is that I have read cgiwrap slows down my script and that there are still potential security issues.
Note: Right now we are on a shared Unix server (at Pair), but will move to a dedicated server when in production. Home directory is set to 711.
So, questions for web-developing monks:
Any other light you can shed on this would be appreciated. Thanks in advance.
Update: fixed title
In reply to Structuring a Web site and security issues by bradcathey
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |