+
+ . This will require very lax permissions in your Bugzilla
+ directories. Run it, instead, as a user with a name, set via your
+ httpd.conf file.
+
Ensure you have adequate access controls for the
- $BUGZILLA_HOME/data/ and $BUGZILLA_HOME/shadow/
- directories, as well as the $BUGZILLA_HOME/localconfig and
- $BUGZILLA_HOME/globals.pl files. The localconfig file
- stores your "bugs" user password, which would be terrible
- to have in the hands of a criminal, while the "globals.pl"
- stores some default information regarding your
- installation which could aid a system cracker. In
- addition, some files under $BUGZILLA_HOME/data/ store
- sensitive information, and $BUGZILLA_HOME/shadow/ stores
- bug information for faster retrieval. If you fail to
- secure these directories and this file, you will expose
- bug information to those who may not be allowed to see it.
-
![]() | Ensure you have adequate access controls for the
+ $BUGZILLA_HOME/data/ directory, as well as the
+ $BUGZILLA_HOME/localconfig file.
+ The localconfig file stores your "bugs" database account password.
+ In addition, some
+ files under $BUGZILLA_HOME/data/ store sensitive information.
+
Bugzilla provides default .htaccess files to protect the
- most common Apache installations. However, you should
- verify these are adequate according to the site-wide
- security policy of your web server, and ensure that the
- .htaccess files are allowed to "override" default
- permissions set in your Apache configuration files.
- Covering Apache security is beyond the scope of this
- Guide; please consult the Apache documentation for
- details.
- Bugzilla provides default .htaccess files to protect the most
+ common Apache installations. However, you should verify these are
+ adequate according to the site-wide security policy of your web
+ server, and ensure that the .htaccess files are allowed to
+ "override" default permissions set in your Apache configuration
+ files. Covering Apache security is beyond the scope of this Guide;
+ please consult the Apache documentation for details.
If you are using a web server that does not support the
- .htaccess control method, you are at
- risk! After installing, check to see if
- you can view the file "localconfig" in your web browser
- (e.g.: If you are using a web server that does not support the
+ .htaccess control method,
+ you are at risk!
+
+ After installing, check to see if you can view the file
+ "localconfig" in your web browser (e.g.:
+ http://bugzilla.mozilla.org/localconfig). If you can read the contents of this file, your web server has not secured your bugzilla directory properly and you must fix this problem before deploying Bugzilla. If, however, it gives you a "Forbidden" error, then it probably respects the .htaccess conventions and you are good to go.
- |
When you run checksetup.pl, the script will attempt to modify various
- permissions on files which Bugzilla uses. If you do not have a
- webservergroup set in the localconfig file, then Bugzilla will have to
- make certain files world readable and/or writable. THIS IS
- INSECURE!. This means that anyone who can get access to
- your system can do whatever they want to your Bugzilla installation.
-
When you run checksetup.pl, the script will attempt to modify
+ various permissions on files which Bugzilla uses. If you do not have
+ a webservergroup set in the localconfig file, then Bugzilla will have
+ to make certain files world readable and/or writable.
+ THIS IS INSECURE!
+
+ . This means that anyone who can get access to your system can do
+ whatever they want to your Bugzilla installation.
This also means that if your webserver runs all cgi scripts as the
- same user/group, anyone on the system who can run cgi scripts will
- be able to take control of your Bugzilla installation.
-
This also means that if your webserver runs all cgi scripts
+ as the same user/group, anyone on the system who can run cgi
+ scripts will be able to take control of your Bugzilla
+ installation.
On Apache, you can use .htaccess files to protect access
- to these directories, as outlined in On Apache, you can use .htaccess files to protect access to
+ these directories, as outlined in
+ Bug 57161 for the localconfig file, and Bug
+ 57161
+
+ for the localconfig file, and
+ Bug 65572 for adequate protection in your data/ and shadow/ directories.
-
Note the instructions which follow are Apache-specific.
- If you use IIS, Netscape, or other non-Apache web servers,
- please consult your system documentation for how to secure
- these files from being transmitted to curious users.
-
Place the following text into a file named ".htaccess",
- readable by your web server, in your $BUGZILLA_HOME/data
- directory.
<Files comments> allow
- from all </Files> deny from all
Bug
+ 65572
- Note the instructions which follow are Apache-specific. If you
+ use IIS, Netscape, or other non-Apache web servers, please consult
+ your system documentation for how to secure these files from being
+ transmitted to curious users.
Place the following text into a file named ".htaccess",
- readable by your web server, in your $BUGZILLA_HOME/
- directory.
Place the following text into a file named ".htaccess",
+ readable by your web server, in your $BUGZILLA_HOME/data directory.
+
<Files localconfig> deny
- from all </Files> allow from all
<Files comments> allow from all </Files>
+ deny from all
-
Place the following text into a file named ".htaccess",
- readable by your web server, in your $BUGZILLA_HOME/shadow
- directory.
Place the following text into a file named ".htaccess",
+ readable by your web server, in your $BUGZILLA_HOME/ directory.
+
deny from all
<Files localconfig> deny from all </Files>
+ allow from all
- Product, Component, Milestone, and Version
- AdministrationGroups and Group Security