From Wikibooks, open books for an open world
Jump to navigation Jump to search

Numerous robots use to try to crack some databases (for instance via PhpMyAdmin or WordPress). To be protected from them, we can play on several criteria.

For example, to forbid to visualize a directory files which hasn't got any index (e.g.: .html, .php), add the code: Options -Indexes.

Protection by provenance[edit | edit source]

Authorize only two IP to read the directory:

whitelist with Require[1][edit | edit source]

    <Directory /usr/share/phpmyadmin/>
        <IfModule mod_authz_core.c>
                Require all denied
                Require ip
                Require ip

whitelist with allow (obsolete in Apache 2.4)[edit | edit source]

    <Directory /usr/share/phpmyadmin/>
        <IfModule mod_access_compat.c>
            deny from all
            allow from
            allow from

If the authorization ranges have some addresses in common with the prohibited ranges, it's better to specify their precedence (the lines order in the .htaccess file doesn't change anything):

order allow, deny
begin by the authorizations and then start the interdictions, by risking to ban what was previously allowed.
order deny, allow
the contrary is less restrictive.

blacklist avec Require[2][edit | edit source]

    <Directory /usr/share/phpmyadmin/>
        <IfModule mod_authz_core.c>
            Require all granted
            Require not ip

blacklist avec deny (obsolete in Apache 2.4)[edit | edit source]

    <Directory /usr/share/phpmyadmin/>
        <IfModule mod_access_compat.c>
            order allow,deny
            allow from all
            deny from

Protection by password[edit | edit source]

Authentication configuration[edit | edit source]

It's imperative to allow the authentication parameters modifications in the Apache settings.

The directive AllowOverride of a parent directory must contain the option AuthConfig[3].

The directives to place in the .htaccess are:

AuthType basic
authentication type communally adopted but poorly secured.
AuthName "My message"
the text as an invite in the dialog box.
AuthUserFile /etc/apache2/my_passwd
the passwords file path.
Require valid-user
specifies that a valid account is needed to accede to the folder.

We can also use Require user toto sasa to authorize only the two accounts toto & sasa.

The authentication type basic uses not crypted passwords.

Some other more secured types exist, like digest, which is recommended to combine with HTTPS.

The first request is addressed to the protected directory and provokes the displaying of the dialog box, from which the user should identify (with login and password):

  • If the password is invalid, the dialog will be displayed again.
  • If it's valid, the navigator can record it, and never ask it again until the next relaunching.

Passwords file[edit | edit source]

The following command creates a passwords file called with one user toto:

htpasswd -c /home/user/www/.htpasswd toto

To add or modify a user:

htpasswd /home/user/www/.htpasswd sasa

Then, tell to .htaccess the .htpasswd path with:

 AuthName "Protected page"
 AuthType Basic
 AuthUserFile "/home/user/www/.htpasswd"
 Require valid-user

References[edit | edit source]

  1. https://httpd.apache.org/docs/2.4/en/howto/access.html
  2. https://httpd.apache.org/docs/2.4/en/upgrading.html
  3. http://httpd.apache.org/docs/2.2/mod/core.html#allowoverride