The Email tracking software that we’re gonna use requires mod_perl however the Apache user (nobody) should has to access to the tracking software’s database configuration file -which stores database passwords- on a shared hosting server other users can read those configuration files via Perl programming; obtaining access to root of the email tracking software.
To resolve this security issue we have to run another instance of Apache with mod_perl and perl-suid then proxy request the alias of tracking software from shared Apache instance.
Would you please help on how to run another instance of Apache (buildapache.sea) safely?
To resolve this security issue we have to run another instance of Apache with mod_perl and perl-suid then proxy request the alias of tracking software from shared Apache instance.
Would you please help on how to run another instance of Apache (buildapache.sea) safely?