I have searched, without success, for the answer to this. If I have missed the answer, I apologize.
In order to have the .pass, .count, .log, .db, .pl, files secure from outside interests I have placed them in a different directory with an .htaccess file
<Files>
Order Deny, Allow
Deny From All
</Files>
If I place a similar file in the directory where db.cgi and default.cfg reside...I cannot use the script ad default.cfg is no longer accessible.
Is there a way to protect the default.cfg file other than simply re-naming it that will still allow it to be accessed by the script.
A Yukoner promoting the Yukon.
In order to have the .pass, .count, .log, .db, .pl, files secure from outside interests I have placed them in a different directory with an .htaccess file
<Files>
Order Deny, Allow
Deny From All
</Files>
If I place a similar file in the directory where db.cgi and default.cfg reside...I cannot use the script ad default.cfg is no longer accessible.
Is there a way to protect the default.cfg file other than simply re-naming it that will still allow it to be accessed by the script.
A Yukoner promoting the Yukon.