[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#207498: apache_1.3.27.0-2 cannot authenticate through PAM (fwd)

Just to keep the bug uptodate...

---------- Forwarded message ----------
Date: Tue, 2 Sep 2003 11:31:31 -0300
From: Margarita Manterola <marga@marga.com.ar>
To: Fabio Massimo Di Nitto <fabbione@fabbione.net>
Subject: Re: Bug#207498: apache_1.3.27.0-2 cannot authenticate through PAM

Hola Fabio Massimo Di Nitto!

> This is not a good idea. It makes it impossible for us to debug or
> reproduce the problem. You need to have a fully upgraded and alligned
> system, reproduce the problem and then open a bug.

I'm sorry, but I needed the server to be functional, it's the server I
use to develop and test my web applications and I cannot have it down
just for the sake of bug tracking.

Anyway, I HAD the upgraded version, and it DIDN'T work.

> Anyway if i will be able to reproduce the problem i will work on a fix. If
> i can't i will need you to upgrade your machine and provide me more
> information.

I have all the information.  It took me more than two days to realize
what the problem was.  So I can tell you what the symptoms were:

* PAM authentication through Apache stopped working.  I upgraded
everything related, no changes.
* I added a PHP PAM module, that does not use libapache-mod-auth-pam,
but goes directly to the PAM api, and it didn't work either.

I had everything up-to-date, only when I downgraded Apache was I able to
authenticate both through PHP and through Basic Authentication.  I
didn't have to upgrade or downgrade anything else, only "apache" and
"apache-common" packages.

It seems that the latest version of Apache is somehow blocking the
access of both an internal module or a PHP module to the PAM API, I have
no idea how such thing could be happening but that's definitely what it
looks like.

Let me know how I can help you reproduce the problem.  I might send you
my configuration files (httpd.conf and .htacces) if you need them.


Reply to: