1 |
On 05/22/2016 04:50 AM, Mick wrote: |
2 |
> |
3 |
> I tried setting APACHE2_MODULES="access_compat" in make.conf and I got this |
4 |
> conflict: |
5 |
|
6 |
Oh, sorry, I meant that you have to add "access_compat" to the list of |
7 |
modules already present in APACHE2_MODULES. |
8 |
|
9 |
Those conflicts are saying that you need "unixd" for php itself, and |
10 |
eselect-php wants "dir". This is a pretty minimal list: |
11 |
|
12 |
APACHE2_MODULES="alias auth_basic auth_digest authn_anon authn_core\ |
13 |
authn_file authz_core authz_host authz_user dir\ |
14 |
include log_config mime rewrite socache_shmcb unixd" |
15 |
|
16 |
(Add access_compat if you want). You can narrow it down by looking |
17 |
through each module's documentation: |
18 |
|
19 |
http://httpd.apache.org/docs/current/mod/ |
20 |
|
21 |
The directives that each one provides are listed over on the right. So |
22 |
if, for example, you don't use "AuthUserFile" in your config, then it's |
23 |
safe to turn off mod_authn_file. |
24 |
|
25 |
The Drupal thing is highly annoying. Their stupid status report ignores |
26 |
the fact that: |
27 |
|
28 |
1. You can achieve the same thing with an htaccess file that isn't |
29 |
byte-for-byte identical to the one they ship. |
30 |
|
31 |
2. If you run multiple sites, you can implement the restrictions in |
32 |
the vhosts and not in htaccess files. |
33 |
|
34 |
3. Not every web server uses htaccess files. |
35 |
|
36 |
I've had to explain to a lot of customers that, yes, their site is |
37 |
secure, that check was just written by idiots. |