This is the mail archive of the
mailing list for the Cygwin project.
RE: mod_auth_mysql (2nd request)
- From: "Bill McCormick" <wpmccormick at covad dot net>
- To: "Cygwin" <cygwin at cygwin dot com>
- Date: Thu, 21 Aug 2003 05:53:40 -0500
- Subject: RE: mod_auth_mysql (2nd request)
- Reply-to: <wpmccormick at covad dot net>
> > Auth_MySQL_Info host user password
> > Auth_MySQL_Encryption_Types Plaintext, Crypt_DES, MySQL
> > <Directory /var/www/htdocs/*/admin>
> > AuthType Basic
> > AuthName "Password Required"
> > Auth_MySQL_DB *
> > Auth_MySQL_Password_Table http_auth
> > Auth_MySQL_Group_Table http_auth
> > Auth_MySQL_Empty_Passwords Off
> > Require Group admins
> > </Directory>
> I didn't get the point what you want to do here?!
I would like to be able to use the [Auth_MySQL_DB *] directive in httpd.conf
to avoid having a .htaccess in each of my users admin directory. (see
example directive above)
> now, I guess you are building apache statically, right? In that case
> you will have to provide the libmysqlclient.a and libz.a as LDFLAGS to
> the build process.
> Another option is to rebuild apache in shared dynamic mode, which will
> create .dll files for each module (even the core).
I expected shared dynamic mode. This is how it comes with the cygwin disto,
right? So I followed the cygwin/apache docs:
I used the recommended configure from the cygwin/apache docs ...
$ ./configure \
... and added the last three parameters.
## Inherited Makefile options from Configure script
## (Begin of automatically generated section)
CFLAGS1=-I/usr/local/mysql/include/mysql -DCYGWIN -DUSE_HSREGEX -DNO_DL_NEE
LIBS1= -L/usr/local/mysql/lib/mysql -L/lib -lz -lmysqlclient -lcrypt -lgdbm
I then made minor changes to LIBS1 section. At the time I wasn't aware that
the libs need to be in LDFLAGS for dynamic build. So did I leave something
out during configure? For dynamic build, should the lib flags be in LDFLAGS1
or EXTRA_LDFLAGS, or it doesn't matter?
> Then you can tweak /usr/local/apache/bin/apxs as it is in the cygwin
> net distribution (this can't be done automatically from the apache
> build process for cygwin unfortunately).
> After you 'make' and 'make install' simply copy the apxs from the
> orginal distribution tree into your build install tree and then use
> apxs to compile the mysql_auth module like
> $ ./apxc -c mod_auth_mysql.c
> in case you need to add LDFLAGS you can pass apxs the -L and -l
> options for the gcc.
> Hope I gave you a good roadmap.
Yes, very helpful, thank you :)
> BTW, why is the recompiling of mysql_auth necessary?
No it's not. However, in the latest ver (2.20), Zeev has changed the apache
directives. He's kindly providing a script to update .htaccess files but I'd
rather avoid that whole mess and go with all the latest as I just now begin
to add password security to my application. Furthermore, in 2.20 there have
been a number of fixes relating to crypt'ing that I'd like to get out of the
Is the versioning the same between the cygwin distro and disto from Zeev?
i.e. does cygwin mod_auth_myslq 1.11-1 == mod_auth_myslq 1.11-1. I didn't
find a 1.11-1 in Zeev's rev history?
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.512 / Virus Database: 309 - Release Date: 8/19/2003
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html