Re: authz / authn and mod_auth_ldap

2003-01-20 Thread Estrade Matthieu
Will it be the same for user,  or will he had to add more modules when 
he will compile his apache ?
I understand it will be the same when he will setup the authentication, 
the Directives will be the same, but if the user forget to compile 
authn, maybe i will not understand why some directives are working and 
not the others.
I understand too it's better to split the code, it will be easier to 
read, so good for all developper like me who are coding apache modules. 
but the documentation must be uptodate with the split.

Last month, i wanted to setup an ldap authentication, i spent many times 
to understand the gap between now and 3 month before when my setup was 
working. The auth changed, i had to use basic auth modules instead of 
before...
And i took hours to find a directive, to let auth_basic make the 
password go to auth_ldap, the directive wasn't on the mod_ldap 
documentation, and was lost in the auth_basic help
So splitting the modules is maybe a good idea, but the right 
documentation must folow...

Regards,

Matthieu



Graham Leggett wrote:

Estrade Matthieu wrote:


I read the discussion for few messages, i am not an apache 
developper, so i will speak as a user. IMHO, Splitting into two 
modules will make auth more complex. actually, it's not really easy 
to setup, and the documentation is not always up to date.


The configuration for users will remain exactly the same as it is now, 
so I don't believe a split will make it any harder for users. It will 
however make the code a lot simpler to read, and hopefully more stable 
as a result.

Regards,
Graham



_
GRAND JEU SMS : Pour gagner un NOKIA 7650, envoyez le mot IF au 61321
(prix d'un SMS + 0.35 euro). Un SMS vous dira si vous avez gagné.
Règlement : http://www.ifrance.com/_reloc/sign.sms




RE: wanted: snapshots from apr-iconv

2003-01-20 Thread Günter Knauf
Hi Sander,
>> From: Gunter Knauf [mailto:[EMAIL PROTECTED]]
>> Sent: Friday, January 17, 2003 7:42 PM

>> Hi,
>>
>> is it possible that we can get also snapshots of apr-iconv at:
>> http://cvs.apache.org/snapshots/
>> ??

> apr-iconv isn't exactly a moving target...  What are you using it
> for (out of interest)?
those people which dont follow the development every day prefer downloading snapshots 
from the snapshot server, they only do a compile after important fixes or changes; and 
for this I've modified Doug's fetch-from-cvs.pl so that it fetches the three archives, 
extracts them into one tree and converts the *.dsp and *.mak files to make MSVC happy; 
and since we need now apr-iconv for Win32 platform I can only download 3 archives as 
snapshots, apr-iconv I have to pull from cvs...

Guenter.




mod_auth_ldap vs mod_ldap (was: Re: authz / authn andmod_auth_ldap)

2003-01-20 Thread Brad Nicholes
While we are on the subject of splitting auth_ldap, does it still make
sense to have mod_auth_ldap and mod_ldap?  Would it make more sense to
combine these two modules.  It seems that the split was initially due to
trying to include the ldap connection caching in apr-util.  Since that
is no longer the case, shouldn't the connection caching be rolled back
into auth_ldap?  It seems like the purpose for having a submodule like
mod_ldap is so that it can be easily replaced.  Do we expect someone to
implement another connection caching scheme?
 Another messy point is that auth_ldap includes apr_ldap.h which resides
in apr-util/include.  Does it make sense to have an apr_ldap.h since
auth_ldap seems to be the only thing that uses it?  It just seems like
ldap functionality was never completely split from APR.  I am just
wondering if this is something else that should be cleaned up before
moving auth_ldap out of experimental.

 

Brad Nicholes
Senior Software Engineer
Novell, Inc., the leading provider of Net business solutions
http://www.novell.com 
>>> [EMAIL PROTECTED] 01/20/03 01:40 AM >>>
Will it be the same for user,  or will he had to add more modules when 
he will compile his apache ?
I understand it will be the same when he will setup the authentication, 
the Directives will be the same, but if the user forget to compile 
authn, maybe i will not understand why some directives are working and 
not the others.
I understand too it's better to split the code, it will be easier to 
read, so good for all developper like me who are coding apache modules. 
but the documentation must be uptodate with the split.

Last month, i wanted to setup an ldap authentication, i spent many times

to understand the gap between now and 3 month before when my setup was 
working. The auth changed, i had to use basic auth modules instead of 
before...
And i took hours to find a directive, to let auth_basic make the 
password go to auth_ldap, the directive wasn't on the mod_ldap 
documentation, and was lost in the auth_basic help
So splitting the modules is maybe a good idea, but the right 
documentation must folow...

Regards,

Matthieu



Graham Leggett wrote:

> Estrade Matthieu wrote:
>
>> I read the discussion for few messages, i am not an apache 
>> developper, so i will speak as a user. IMHO, Splitting into two 
>> modules will make auth more complex. actually, it's not really easy 
>> to setup, and the documentation is not always up to date.
>
>
> The configuration for users will remain exactly the same as it is now,

> so I don't believe a split will make it any harder for users. It will 
> however make the code a lot simpler to read, and hopefully more stable

> as a result.
>
> Regards,
> Graham



_
GRAND JEU SMS : Pour gagner un NOKIA 7650, envoyez le mot IF au 61321
(prix d'un SMS + 0.35 euro). Un SMS vous dira si vous avez gagné.
Règlement : http://www.ifrance.com/_reloc/sign.sms





2.0.40 build

2003-01-20 Thread Enrico Weigelt

hi folks, 

there's an little bug in the apache buildsystem (2.0.40):

* --enable-ssl is not able to find ssl in the default location (/usr)
  automatically, so --with-ssl=/usr/ is necessary.
  
* --enable-dav-fs requires --enable-dav, but does not enable it
  automatically, instead produces 'undefined reference' in link stage
  
* same w/ --enable-mem-cache

cu
-- 
-
 Enrico Weigelt==   metux ITS 
 Webhosting ab 5 EUR/Monat.  UUCP, rawIP und vieles mehr.

 phone: +49 36207 519931 www:   http://www.metux.de/ 
 fax:   +49 36207 519932 email: [EMAIL PROTECTED]
 cellphone: +49 174 7066481  smsgate:   [EMAIL PROTECTED]
-
 Diese Mail wurde mit UUCP versandt.  http://www.metux.de/uucp/



Re: [patch] rfc1413/mod_ident

2003-01-20 Thread William A. Rowe, Jr.
At 01:02 AM 1/19/2003, you wrote:

>Propagate the rfc1413/mod_ident changes to Windows.

Committed, thanks.

I reinvented mod_ident.dsp.  I also reinvented mod_ident.exp.  Hopefully
my guesses are correct.  These files came across as;

? modules/metadata/mod_ident.dsp
? modules/metadata/mod_ident.exp

If you cvs add the modules, then cvs diff -N you will get those new (and
any removed) sources included in the diff output.

Thanks again,

Bill 




Re: [patch] rfc1413/mod_ident

2003-01-20 Thread David Shane Holden
William A. Rowe, Jr. wrote:

If you cvs add the modules, then cvs diff -N you will get those new (and
any removed) sources included in the diff output.


I tried that, but got a 'write access required' error so I just attached 
the new files.

Shane



Re: [patch] rfc1413/mod_ident

2003-01-20 Thread William A. Rowe, Jr.
At 03:54 PM 1/20/2003, David Shane Holden wrote:
>William A. Rowe, Jr. wrote:
>>If you cvs add the modules, then cvs diff -N you will get those new (and
>>any removed) sources included in the diff output.
>
>I tried that, but got a 'write access required' error so I just attached the new 
>files.

Ahhh... now I see that.  Sorry I missed it on the first pass.

FWIW... I usually insert the files into the CVS/Entries file of that directory, 
the stubs look like;

/new_filename.c/0/dummy timestamp//

which are simple enough to dummy up :-)

Also Win32 seems to be building mod_ident just fine.  Thank you again.

Bill






httpd 2.0.44 compile error

2003-01-20 Thread solo turn
there is a compile error on solaris 2.8:

/bin/bash /home/src/httpd-2.0.44/srclib/apr/libtool --silent
--mode=compile cc  -g -mt-DSOLARIS2=8 -D_POSIX_PTHREAD_SEMANTICS
-D_REENTRANT-I/home/src/httpd-2.0.44/srclib/apr/include
-I/home/src/httpd-2.0.44/srclib/apr-util/include
-I/home/local/include
-I/home/src/httpd-2.0.44/srclib/apr-util/xml/expat/lib -I.
-I/home/src/httpd-2.0.44/os/unix
-I/home/src/httpd-2.0.44/server/mpm/prefork
-I/home/src/httpd-2.0.44/modules/http
-I/home/src/httpd-2.0.44/modules/filters
-I/home/src/httpd-2.0.44/modules/proxy
-I/home/src/httpd-2.0.44/include -I/home/local/include/openssl
-I/home/src/httpd-2.0.44/modules/dav/main -prefer-non-pic -static -c
request.c && touch request.lo
"core.c", line 184: undefined struct/union member: enable_sendfile
"core.c", line 184: undefined symbol: ENABLE_SENDFILE_UNSET
"core.c", line 451: undefined struct/union member: enable_sendfile
"core.c", line 451: undefined symbol: ENABLE_SENDFILE_UNSET
"core.c", line 452: improper member use: enable_sendfile
"core.c", line 452: improper member use: enable_sendfile
"core.c", line 1477: undefined struct/union member: enable_sendfile
"core.c", line 1477: undefined symbol: ENABLE_SENDFILE_ON
"core.c", line 1480: undefined struct/union member: enable_sendfile
"core.c", line 1480: undefined symbol: ENABLE_SENDFILE_OFF
"core.c", line 3314: undefined struct/union member: deliver_script
"core.c", line 3326: undefined struct/union member: enable_sendfile
"core.c", line 3326: undefined symbol: ENABLE_SENDFILE_OFF
"core.c", line 3653: cannot recover from previous errors


did i miss something about this? i did
./buildconf
./configure --prefix=/home/local --enable-so --enable-dav
--enable-deflate --enable-ssl --with-ssl=/home/local --with-dbm=db4
--with-berkeley-db=/home/local

like with version 2.0.43


__
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com



Re: httpd 2.0.44 compile error

2003-01-20 Thread Jeff Trawick

solo turn wrote:


there is a compile error on solaris 2.8:

/bin/bash /home/src/httpd-2.0.44/srclib/apr/libtool --silent
--mode=compile cc  -g -mt-DSOLARIS2=8 -D_POSIX_PTHREAD_SEMANTICS
-D_REENTRANT-I/home/src/httpd-2.0.44/srclib/apr/include
-I/home/src/httpd-2.0.44/srclib/apr-util/include
-I/home/local/include


whoops, /home/local/include is searched before Apache directories...
any chance you have a previous Apache install there?  you're probably
picking up old levels of Apache header files, and ENABLE_SENDFILE_*
wasn't defined in 2.0.43


-I/home/src/httpd-2.0.44/srclib/apr-util/xml/expat/lib -I.
-I/home/src/httpd-2.0.44/os/unix
-I/home/src/httpd-2.0.44/server/mpm/prefork
-I/home/src/httpd-2.0.44/modules/http
-I/home/src/httpd-2.0.44/modules/filters
-I/home/src/httpd-2.0.44/modules/proxy
-I/home/src/httpd-2.0.44/include -I/home/local/include/openssl
-I/home/src/httpd-2.0.44/modules/dav/main -prefer-non-pic -static -c
request.c && touch request.lo
"core.c", line 184: undefined struct/union member: enable_sendfile
"core.c", line 184: undefined symbol: ENABLE_SENDFILE_UNSET