apache2 (2.4.10-2) unstable; urgency=low
The default period for which rotated log files are kept has been
reduced from one year to 14 days.
-- Stefan Fritsch <sf(a)debian.org> Tue, 23 Sep 2014 22:25:06 +0200
apache2 (2.4.1-1) unstable; urgency=low
This package introduces a new major release of the Apache HTTP server. It is
likely the site configuration needs changes to work with this release.
Notable changes which need special care are:
The module interface (ABI) has changed. If you have any locally compiled
modules, you have to re-compile them for apache2 2.4.
The authorization and authentication system has changed. Existing
configurations using deprecated Order/Allow/Deny directives need to be
upgraded to the new system. Please review upstream's "Authentication,
Authorization and Access Control Howto" [1]. There is a new module
"mod_access_compat", which is supposed to provide backward compatibility,
but it does not work well in practice.
Furthermore, MPMs are simple modules now. Thus, the MPM can be changed
at any time by (un-)loading a specific module. Be careful when upgrading. An
example of changing the MPM is given below:
a2dismod mpm_worker
a2enmod mpm_prefork
MPM ITK users should be advised, that ITK is not a MPM anymore. Instead, it
is a simple Apache module, expanding functionality of the prefork MPM. Thus,
users should switch to the prefork MPM and enable ITK as a module. The
upgrade scripts ensure this for the upgrade from Debian Wheezy.
We did change the security model for Apache in our default configuration. We
do not allow access to the file system outside /var/www and /usr/share.
If you are running virtual hosts or scripts outside these directories, you
need to whitelist them in your configuration to grant access through HTTP.
Special care must be taken if you are using a sub-directory in /srv to serve
your content as recommended by the File Hierarchy Standard (FHS). You must
allow access to your served directory explicity in the corresponding virtual
host, or by allowing access in apache2.conf as proposed.
Along the security model, we did also change the default Document Root, files
are served from. Previous releases served /var/www by default when no other
virtual host matched the request. Starting with this release, we changed the
default document root to /var/www/html, so that sensitive files from other
virtual hosts wich are typically put into some directory below /var/www are
not exposed by the default virtual host. This change further improves the out
of box security.
Moreover, the configuration mechanism in Debian has changed. All
configurations in sites-enabled and conf-enabled need a ".conf" suffix now.
The latter replaces the deprecated /etc/apache2/conf.d/ directory (which is
not supported any more) and works just like {sites,mods}-{available,enabled}
via the "a2enconf" tool. The upgrade tries to migrate known configuration
files from /etc/apache2/conf.d/ to /etc/apache2/conf-available/ - please
review these changes.
Note this means all existing sites are ignored until they get a ".conf"
suffix and are re-enabled by the use of a2ensite. The script in [3] can
automate that for simple cases. This change also includes Debian default
sites, so the default site has been renamed to 000-default to avoid naming
confusions. The rename of the config files to *.conf makes the special
handling inside apache2 to ignore *.dpkg-* backup files obsolete. This
special handling has been removed.
Users of mod_authn_dbm should switch to htdbm to manage their DBM user
databases. The pure-perl management utility "dbmmanage" was removed as it was
outdated and orphaned upstream.
Packagers are advised to review whether their packages comply with this
new version. Please see [2] for detailed documentation and instructions.
[1] http://httpd.apache.org/docs/2.4/howto/auth.html
[2] </usr/share/doc/apache2/PACKAGING>
[3] </usr/share/doc/apache2/migrate-sites.pl>
-- Arno Töll <arno(a)debian.org> Fri, 23 July 2012 23:50:13 +0200