|
Home > Archive > Debian Developers > November 2006 > release critical bug in apache2.2?
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
release critical bug in apache2.2?
|
|
| Bastian Venthur 2006-11-02, 1:18 pm |
| Hi
I've just upgraded #393913 from minor to important.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=393913
Somebody just mailed me that this bug is release critical since it
allows to read/download php-scripts (like index.php).
Can somebody confirm that this bug is RC or should I just keep it important?
Cheers,
Bastian
PS: A patch is also included to fix this bug, it is a one-liner.
--
Bastian Venthur
http://venthur.de
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
| |
| Mike Hommey 2006-11-02, 1:18 pm |
| On Thu, Nov 02, 2006 at 03:32:39PM +0100, Bastian Venthur <expires-2007@venthur.de> wrote:
> Hi
>
> I've just upgraded #393913 from minor to important.
>
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=393913
>
> Somebody just mailed me that this bug is release critical since it
> allows to read/download php-scripts (like index.php).
>
> Can somebody confirm that this bug is RC or should I just keep it important?
DirectoryIndex tells apache which file(s) it may use when the url points
to a directory, instead of creating an index of the directory itself, if
allowed to.
The default value for DirectoryIndex is index.html, which
obviously forgets index.php. But that doesn't mean index.php will be
readable as source. It only means that the auto index will be displayed
if no index.html is present and if allowed to.
Auto-indexes are enabled only in /var/www/apache2-default and
/usr/share/apache2/icons by default, so it is not likely to leak any
unexpected file list.
So no, that doesn't grant an RC bug for these reasons.
On the other hand, it breaks configurations that used to work... (sites
relying on this index.php setting will get 403 errors after upgrade from
2.0)
Mike
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
| |
| sean finney 2006-11-02, 7:21 pm |
| On Thu, 2006-11-02 at 19:20 +0100, Mike Hommey wrote:
> Auto-indexes are enabled only in /var/www/apache2-default and
> /usr/share/apache2/icons by default, so it is not likely to leak any
> unexpected file list.
>
> So no, that doesn't grant an RC bug for these reasons.
>
> On the other hand, it breaks configurations that used to work... (sites
> relying on this index.php setting will get 403 errors after upgrade from
> 2.0)
i imagine the apache maintainers will argue that it should be either (a)
the webapp package or (b) the php apache module's repsonsibility
to specify the additional DirectoryIndex.
iirc DirectoryIndex does/can append to the list of index files, right?
if so i'd have no problem slipping this into the php/apache module
configuration files if that's the agreed course of action. but whether
or not this makes it to etch is an open question.
sean
| |
| Bastian Venthur 2006-11-02, 7:21 pm |
| Mike Hommey wrote:
> On Thu, Nov 02, 2006 at 03:32:39PM +0100, Bastian Venthur <expires-2007@venthur.de> wrote:
> DirectoryIndex tells apache which file(s) it may use when the url points
> to a directory, instead of creating an index of the directory itself, if
> allowed to.
>
> The default value for DirectoryIndex is index.html, which
> obviously forgets index.php. But that doesn't mean index.php will be
> readable as source. It only means that the auto index will be displayed
> if no index.html is present and if allowed to.
Is this upstreams default or our? I mean I just cannot imagine that
apache ignores index.php files by default.
>
> Auto-indexes are enabled only in /var/www/apache2-default and
> /usr/share/apache2/icons by default, so it is not likely to leak any
> unexpected file list.
>
But on the other side, isn't it quite usual to have an index.php in some
dir, say /var/www/ while the document root of your domain just points to
/var/www?
In this case the whole directory structure is visible to every user
including the the file index.php itself.
> So no, that doesn't grant an RC bug for these reasons.
>
> On the other hand, it breaks configurations that used to work... (sites
> relying on this index.php setting will get 403 errors after upgrade from
> 2.0)
So, was the change intentional or just a mistake?
Bastian
--
Bastian Venthur
http://venthur.de
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
| |
| Mike Hommey 2006-11-02, 7:21 pm |
| On Thu, Nov 02, 2006 at 08:05:08PM +0100, Bastian Venthur <expires-2007@venthur.de> wrote:
> Mike Hommey wrote:
>
> Is this upstreams default or our? I mean I just cannot imagine that
> apache ignores index.php files by default.
Upstream defaults to:
<IfModule dir_module>
DirectoryIndex index.html
</IfModule>
PHP is shipped with upstream apache, so there is no reason that it
should support index.php files.
Mike
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
| |
| Mike Hommey 2006-11-02, 7:21 pm |
| On Thu, Nov 02, 2006 at 08:16:46PM +0100, sean finney <seanius@debian.org> wrote:
> On Thu, 2006-11-02 at 19:20 +0100, Mike Hommey wrote:
>
> i imagine the apache maintainers will argue that it should be either (a)
> the webapp package or (b) the php apache module's repsonsibility
> to specify the additional DirectoryIndex.
Yes, that would be a good idea.
> iirc DirectoryIndex does/can append to the list of index files, right?
Yes, it does
> if so i'd have no problem slipping this into the php/apache module
> configuration files if that's the agreed course of action. but whether
> or not this makes it to etch is an open question.
What is sure is that we should not break existing configurations on
upgrade.
Mike
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
| |
| Kris Deugau 2006-11-02, 7:21 pm |
| sean finney wrote:
> i imagine the apache maintainers will argue that it should be either (a)
> the webapp package or (b) the php apache module's repsonsibility
> to specify the additional DirectoryIndex.
>
> iirc DirectoryIndex does/can append to the list of index files, right?
This is exactly what I did for a set of custom Apache2+PHP packages; it
works fine.
-kgd
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
| |
| Mike Hommey 2006-11-02, 7:21 pm |
| On Thu, Nov 02, 2006 at 09:39:39PM +0100, Mike Hommey <mh@glandium.org> wrote:
> On Thu, Nov 02, 2006 at 08:05:08PM +0100, Bastian Venthur <expires-2007@venthur.de> wrote:
>
> Upstream defaults to:
> <IfModule dir_module>
> DirectoryIndex index.html
> </IfModule>
>
> php is shipped with upstream apache, so there is no reason that it
^^^
Err, php is *not* shipped.
Mike
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
| |
| Bastian Venthur 2006-11-02, 7:21 pm |
| Mike Hommey wrote:
> There has never been index.php in the DirectoryIndex configuration from
> apache. Adding it is part of the php installation procedure.
Maybe I'm just confusing something but the bugreport claims that the
following line was present in apache2.conf before the upgrade to 2.2 but
not afterwards:
DirectoryIndex index.html index.cgi index.pl index.php index.xhtml
Am I missing something?
Cheers,
Bastian
--
Bastian Venthur http://venthur.de
Debian Developer venthur at debian org
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
| |
| Mike Hommey 2006-11-02, 7:21 pm |
| On Thu, Nov 02, 2006 at 09:50:09PM +0100, Bastian Venthur <venthur@debian.org> wrote:
> Mike Hommey wrote:
>
> Hmm interisting and very disturbing too, since most (if not all) web
> applications I've seen and used seem to silently require that index.php
> files are treated automatically like index.html files. Which seemd to be
> true for pre-2.2 apache versions.
There has never been index.php in the DirectoryIndex configuration from
apache. Adding it is part of the php installation procedure.
Mike
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
| |
| Bastian Venthur 2006-11-02, 7:21 pm |
| Mike Hommey wrote:
>
> Upstream defaults to:
> <IfModule dir_module>
> DirectoryIndex index.html
> </IfModule>
>
> php is shipped with upstream apache, so there is no reason that it
> should support index.php files.
Hmm interisting and very disturbing too, since most (if not all) web
applications I've seen and used seem to silently require that index.php
files are treated automatically like index.html files. Which seemd to be
true for pre-2.2 apache versions.
BTW what's with index.htm (without the l) files? They are not mentioned
there too but they definitely should, don't they?
Anyway, maybe there is a reason upstream decided to change this behavior
or maybe it's just a bug, but I still think we should somehow prepare
our users to this change or better, just be backwards compatible since
it does not really hurt in this case, does it?
Cheers,
Bastian
--
Bastian Venthur http://venthur.de
Debian Developer venthur at debian org
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
| |
| Mike Hommey 2006-11-02, 7:21 pm |
| On Thu, Nov 02, 2006 at 10:08:46PM +0100, Bastian Venthur <venthur@debian.org> wrote:
> Mike Hommey wrote:
>
> Maybe I'm just confusing something but the bugreport claims that the
> following line was present in apache2.conf before the upgrade to 2.2 but
> not afterwards:
>
> DirectoryIndex index.html index.cgi index.pl index.php index.xhtml
>
> Am I missing something?
That was debian specific.
Mike
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
| |
| Brian May 2006-11-02, 7:21 pm |
| >>>>> "Mike" == Mike Hommey <mh@glandium.org> writes:
Mike> Auto-indexes are enabled only in /var/www/apache2-default and
Mike> /usr/share/apache2/icons by default, so it is not likely to leak any
Mike> unexpected file list.
.... on my system autoindexes were enabled by default in my existing
virtual host configurations. Not sure why I did this. Now fixed.
Potentially confusing to visitors before I woke up and realized the
problem (when testing it my bookmark went directly to the index.php
file where it looked OK).
Mike> So no, that doesn't grant an RC bug for these reasons.
A potentially confusing bug.
As to if this bug gets fixed in Etch or not, I really don't care. I
have already solve the problem on my systems...
--
Brian May <bam@debian.org>
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
| |
| Jean-Christophe Dubacq 2006-11-03, 1:27 am |
| On Thu, Nov 02, 2006 at 07:20:12PM +0100, Mike Hommey wrote:
> On Thu, Nov 02, 2006 at 03:32:39PM +0100, Bastian Venthur <expires-2007@venthur.de> wrote:
>
> DirectoryIndex tells apache which file(s) it may use when the url points
> to a directory, instead of creating an index of the directory itself, if
> allowed to.
>
> The default value for DirectoryIndex is index.html, which
> obviously forgets index.php. But that doesn't mean index.php will be
> readable as source. It only means that the auto index will be displayed
> if no index.html is present and if allowed to.
>
> Auto-indexes are enabled only in /var/www/apache2-default and
> /usr/share/apache2/icons by default, so it is not likely to leak any
> unexpected file list.
>
> So no, that doesn't grant an RC bug for these reasons.
>
> On the other hand, it breaks configurations that used to work... (sites
> relying on this index.php setting will get 403 errors after upgrade from
> 2.0)
I remember that since the change, I had to make changes to several php
applications, because at the same time the default configuration did not
include any configuration in the case where php is not installed as
module but (e.g.) as CGI. phpmyadmin by default had a snippet in
..htaccess that was basically:
<IfModule mod_cgi.c>
AddType application/x-httpd-php .php
Action application/x-httpd-php /cgi-bin/php
</IfModule>
<IfModule mod_cgid.c>
AddType application/x-httpd-php .php
Action application/x-httpd-php /cgi-bin/php
</IfModule>
I had to put something of the same sort in phppgaccess, for example, as
well as DirectoryIndex index.php.
Since the change for DirectoryIndex happend at the same time, it might
be this that the user has seen. So the disappearance of index.php may
not be RC; however, the treatement of php as CGI is more likely to be
RC.
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
| |
| Mike Hommey 2006-11-03, 1:27 am |
| On Fri, Nov 03, 2006 at 07:43:36AM +0100, Jean-Christophe Dubacq <jcdubacq1@free.fr> wrote:
> I remember that since the change, I had to make changes to several php
> applications, because at the same time the default configuration did not
> include any configuration in the case where php is not installed as
> module but (e.g.) as CGI. phpmyadmin by default had a snippet in
> .htaccess that was basically:
> <IfModule mod_cgi.c>
> AddType application/x-httpd-php .php
>
> Action application/x-httpd-php /cgi-bin/php
> </IfModule>
> <IfModule mod_cgid.c>
> AddType application/x-httpd-php .php
>
> Action application/x-httpd-php /cgi-bin/php
> </IfModule>
>
> I had to put something of the same sort in phppgaccess, for example, as
> well as DirectoryIndex index.php.
>
> Since the change for DirectoryIndex happend at the same time, it might
> be this that the user has seen. So the disappearance of index.php may
> not be RC; however, the treatement of php as CGI is more likely to be
> RC.
If you install the debian package for php, it is configured as module,
and works fine, so that can't be RC. The only problem is DirectoryIndex.
Mike
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
| |
| Tollef Fog Heen 2006-11-04, 1:25 am |
| Bastian Venthur skrev:
> Is this upstreams default or our? I mean I just cannot imagine that
> apache ignores index.php files by default.
Why not?
> So, was the change intentional or just a mistake?
That it was removed completely was a mistake. That it doesn't include
index.php is not a mistake.
- tfheen
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
| |
| Bastian Venthur 2006-11-05, 7:19 am |
| On 02.11.2006 20:16 schrieb sean finney:
> On Thu, 2006-11-02 at 19:20 +0100, Mike Hommey wrote:
>
> i imagine the apache maintainers will argue that it should be either (a)
> the webapp package or (b) the php apache module's repsonsibility
> to specify the additional DirectoryIndex.
>
> iirc DirectoryIndex does/can append to the list of index files, right?
> if so i'd have no problem slipping this into the php/apache module
> configuration files if that's the agreed course of action. but whether
> or not this makes it to etch is an open question.
Is it possible that adding an updated DirectoryIndex does not fix the
whole bug? Although it fixes the problem that index.php files are not
recognized when entering a certain directory, I noticed that accessing a
php file directly like
http://somedomain.tld/index.php
The file does not get executed as expected, but the browser wants to
download it (which might be a security issue).
Cheers,
Bastian
--
Bastian Venthur http://venthur.de
Debian Developer venthur at debian org
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
| |
| Mike Hommey 2006-11-05, 7:19 am |
| On Sun, Nov 05, 2006 at 01:38:21PM +0100, Bastian Venthur <venthur@debian.org> wrote:
> On 02.11.2006 20:16 schrieb sean finney:
>
> Is it possible that adding an updated DirectoryIndex does not fix the
> whole bug? Although it fixes the problem that index.php files are not
> recognized when entering a certain directory, I noticed that accessing a
> php file directly like
>
> http://somedomain.tld/index.php
>
> The file does not get executed as expected, but the browser wants to
> download it (which might be a security issue).
Then it is likely that you don't have php installed.
Mike
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
| |
| Bastian Venthur 2006-11-05, 1:15 pm |
| On 05.11.2006 14:04 schrieb Mike Hommey:
> On Sun, Nov 05, 2006 at 01:38:21PM +0100, Bastian Venthur <venthur@debian.org> wrote:
>
> Then it is likely that you don't have php installed.
Here is what I've installed:
# dpkg --list | grep php | cut -d " " -f -3
ii libapache2-mod-php5
ii php5
ii php5-common
and:
# cat /etc/apache2/sites-enabled/wiki
<VirtualHost *:80>
ServerName wiki.localhost
ServerAlias wiki.*
DocumentRoot /var/www/wiki/
# Workaround #393913
DirectoryIndex index.html index.cgi index.pl index.php index.xhtml
</VirtualHost>
The index.php lies directly in /var/www/wiki/
The rest is pretty much standard configuration and worked perfectly
before 2.2.
Again, I'm certainly no apache-pro but I think something is wrong here
and since this is already in testing we should make sure to fix it
before it gets stable.
Cheers,
Bastian
--
Bastian Venthur http://venthur.de
Debian Developer venthur at debian org
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
| |
| sean finney 2006-11-05, 1:15 pm |
| On Sun, 2006-11-05 at 14:04 +0100, Mike Hommey wrote:
>
> Then it is likely that you don't have php installed.
*or* that php is installed but not the modules isn't loaded
into $apache *or* that it's installed and loaded but $apache
hasn't been restarted.
the php apache SAPI modules *should* restart apache though. if
they didn't it may be related to #396873 in which the postinst script
for the latest php version has accidentally gone AWOL from
some of the SAPI packages (fix coming shortly).
sean
| |
| Mike Hommey 2006-11-05, 1:15 pm |
| On Sun, Nov 05, 2006 at 02:36:02PM +0100, Bastian Venthur <venthur@debian.org> wrote:
> Here is what I've installed:
> # dpkg --list | grep php | cut -d " " -f -3
> ii libapache2-mod-php5
> ii php5
> ii php5-common
>
> and:
>
> # cat /etc/apache2/sites-enabled/wiki
> <VirtualHost *:80>
> ServerName wiki.localhost
> ServerAlias wiki.*
>
> DocumentRoot /var/www/wiki/
>
> # Workaround #393913
> DirectoryIndex index.html index.cgi index.pl index.php index.xhtml
> </VirtualHost>
>
> The index.php lies directly in /var/www/wiki/
>
> The rest is pretty much standard configuration and worked perfectly
> before 2.2.
What about /etc/apache2/mod-enabled/php5.* ?
> Again, I'm certainly no apache-pro but I think something is wrong here
> and since this is already in testing we should make sure to fix it
> before it gets stable.
I had no problem except the index.php thing when upgrading apache 2.0 +
php4 to apache 2.2 + php4. Maybe there is a problem with php5, or maybe
you upgraded apache before php5 was ready for it and it got disabled
because incompatible...
Mike
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
| |
| Bastian Venthur 2006-11-05, 1:15 pm |
| On 05.11.2006 14:44 schrieb Mike Hommey:
> On Sun, Nov 05, 2006 at 02:36:02PM +0100, Bastian Venthur <venthur@debian.org> wrote:
>
> What about /etc/apache2/mod-enabled/php5.* ?
The symlinks php5.conf and php5.load exist in this dir.
Interisting sidenote:
localhost/index.php does not work, while
localhost/index.php/ does.
Cheers,
Bastian
--
Bastian Venthur http://venthur.de
Debian Developer venthur at debian org
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
| |
| Bastian Venthur 2006-11-05, 1:15 pm |
| On 05.11.2006 14:49 schrieb sean finney:
> On Sun, 2006-11-05 at 14:04 +0100, Mike Hommey wrote:
>
> *or* that php is installed but not the modules isn't loaded
> into $apache *or* that it's installed and loaded but $apache
> hasn't been restarted.
The modules are loaded and apache was restarted maaaany times.
I've even replaced php5 with php4 in order to test wheter there is
something wrong with php5 but with no results.
Cheers,
Bastian
--
Bastian Venthur http://venthur.de
Debian Developer venthur at debian org
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
| |
| Jean-Christophe Dubacq 2006-11-05, 1:15 pm |
|
Le 5 nov. 06 =E0 14:49, sean finney a =E9crit :
> On Sun, 2006-11-05 at 14:04 +0100, Mike Hommey wrote:
>
> *or* that php is installed but not the modules isn't loaded
> into $apache *or* that it's installed and loaded but $apache
> hasn't been restarted.
Or that php is installed as CGI. All the web applications (packaged =20
by Debian) should take care of this case.
--=20
JCD
| |
| Bastian Venthur 2006-11-05, 7:21 pm |
| Bastian Venthur wrote:
> On 02.11.2006 20:16 schrieb sean finney:
>
> Is it possible that adding an updated DirectoryIndex does not fix the
> whole bug? Although it fixes the problem that index.php files are not
> recognized when entering a certain directory, I noticed that accessing a
> php file directly like
>
> http://somedomain.tld/index.php
>
> The file does not get executed as expected, but the browser wants to
> download it (which might be a security issue).
Damn. The problem was my browser, still caching the old page. Clearing
the browserchache solved this problem.
Sorry :/
But the DirectoryIndex problem should be fixed nevertheless.
Cheers,
Bastian
--
Bastian Venthur http://venthur.de
Debian Developer venthur at debian org
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
| |
| Luca Capello 2006-11-06, 1:27 am |
| | |
| Mike Hommey 2006-11-06, 7:19 am |
| On Sun, Nov 05, 2006 at 10:48:10PM +0100, Luca Capello <luca@pca.it> wrote:
> Hello!
>
> On Sun, 05 Nov 2006 21:13:14 +0100, Bastian Venthur wrote:
>
> FWIW, I've the following for apache2.2 on my sid:
> =====
> luca@gismo:~$ grep -r index.html /etc/apache2/*
> /etc/apache2/mods-available/dir.conf: \
> DirectoryIndex index.html index.cgi index.pl index.php index.xhtml
> luca@gismo:~$
> =====
>
> BTW, I didn't manually touch any configuration files and I tried also
> to purge apache2.2-common: the result is always the same,
> /etc/apache2/mods-available/dir.conf contains that line [1].
Good catch, but there is no link in /etc/apache2/mods-enabled...
Anyways, coming back to what we said in a subthread, it would be better
if the DirectoryIndex was split and set by the concerned modules...
index.cgi by the cgi module, index.php by the php module, etc.
Mike
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
| |
| Bastian Venthur 2006-11-06, 7:19 am |
| Mike Hommey wrote:
> On Sun, Nov 05, 2006 at 10:48:10PM +0100, Luca Capello <luca@pca.it> wrote:
>
> Good catch, but there is no link in /etc/apache2/mods-enabled...
.... which might actually be the bug I'm ranting about. Thanks for
finding it Luca.
> Anyways, coming back to what we said in a subthread, it would be better
> if the DirectoryIndex was split and set by the concerned modules...
> index.cgi by the cgi module, index.php by the php module, etc.
Maybe, but I think it's more important to fix the bug as quickly as
possible, since it is already in testing so close before the freeze.
--
Bastian Venthur http://venthur.de
Debian Developer venthur at debian org
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
|
|
|
|
|