Disabling Remote Access to Bugzilla Configuration Files
There are many files that are placed in the Bugzilla directory area that should not be accessible from the web server. Because of the way Bugzilla is currently layered out, the list of what should and should not be accessible is rather complicated. A quick way is to run testserver.pl to check if your web server serves Bugzilla files as expected. If not, you may want to follow the few steps below.
Bugzilla ships with the ability to create .htaccess files that enforce these rules.
- In the main Bugzilla directory, you should:
Block: *.pl, *localconfig*
- In data:
Block everything
- In data/webdot:
- If you use a remote webdot server:
Block everything
But allow *.dot only for the remote webdot server
- Otherwise, if you use a local GraphViz:
Block everything
But allow: *.png, *.gif, *.jpg, *.map
- And if you don’t use any dot:
Block everything
- In Bugzilla:
Block everything
- In template:
Block everything
Be sure to test that data that should not be accessed remotely is properly blocked. Of particular interest is the localconfig file which contains your database password. Also, be aware that many editors create temporary and backup files in the working directory and that those should also not be accessible. To test, simply run testserver.pl, as said above.
A great career is just a certification away. So, practice and validate your skills to become Certified Bugzilla Testing Professional
