From: Wolfgang Apolinarski <wolfgang@apolinarski.de>
To: development@lists.ipfire.org
Subject: Re: [PATCH v2 2/2] Update to apache 2.4.25
Date: Thu, 18 May 2017 21:28:43 +0200 [thread overview]
Message-ID: <001301d2d00c$f65a6570$e30f3050$@apolinarski.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1354 bytes --]
Hi!
> this looks good and I think it is ready to be merged unless anybody
> else has any objections.
>
> I do have one question tho: Do we need to enable all these new modules
> there? The point is that fewer modules would give us less attack
> surface.
>
The modules added by me are:
> > +LoadModule socache_shmcb_module /usr/lib/apache/mod_socache_shmcb.so
This module is a memory-based cache provider for the SSLSessionCache.
> > +LoadModule unixd_module /usr/lib/apache/mod_unixd.so
This module is needed, because of the Group and User directive that change the user/group of Apache after startup (in uid.conf).
> > +LoadModule authn_core_module /usr/lib/apache/mod_authn_core.so
This module provides common authentication methods (AuthType, AuthName).
> > +LoadModule authz_core_module /usr/lib/apache/mod_authz_core.so
This module provides the Require-directive.
>From the existing modules, it is possible to deactivate:
auth_digest_module - I never saw anyone using digest authentication (basic is the one that is commonly chosen)
autoindex_module - Since we are not using the fancy indexing features of apache
Do we actually need the php5 module? ;-)
The web interface does not need it, but apparently a lot of packages need it...
Additionally, cgi was substituted with cgid.
Best regards,
Wolfgang
next reply other threads:[~2017-05-18 19:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-18 19:28 Wolfgang Apolinarski [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-05-17 18:14 [PATCH v2 1/2] apr and aprutil: Added as requirement for apache 2.4 Wolfgang Apolinarski
2017-05-17 18:14 ` [PATCH v2 2/2] Update to apache 2.4.25 Wolfgang Apolinarski
2017-05-18 17:38 ` Michael Tremer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='001301d2d00c$f65a6570$e30f3050$@apolinarski.de' \
--to=wolfgang@apolinarski.de \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox