LD_PRELOAD for modules
Hi, I want to override a library that is linked with an Apache module, i.e. I want to use my modified version of the MySQL client library for example for mod_php. I would like to do this without relinking or even modifying the mod_php lib. I was hoping that I could use something like LD_PRELOAD to force my modified MySQL client library. Is there a way to do this? Thank you, Andrej
Adding a new module to the build
I added my new proposed module to modules/aaaconfig.m4, but that only got the module build--not installed--even when --enable-auth-cert is included in my configure options. I need to re-run buildconf, and I'm getting a bunch of warnings such as: autoheader: WARNING: Using auxiliary files such as `acconfig.h', `config.h.bot' [...] is deprecated and discuraged [...] autoheader: WARNING: Using the third argument of `AC_DEFINE' and [...] `AC_DEFINE_UNQUOTED' allows one to define a template without [...] `acconfig.h': [...] configure.in.57: warning: LTOPTIONS_VERSION is m4_required'd but not m4_defun'd aclocal.m4:69: LT_INIT is expanded from... aclocal.m4:104: AC_PROG_LIBTOOL is expanded from... Configure.in:57 the top level I also get similar warnings for LTSUGAR_VERSION, LTVERSION_VERSION, LTOBSOLETE_VERSION, LT_OPTIONS_VERSION There are four errors, all possibly undefined macro for the following: AC_LIBTOOL_WIN32_DLL, m4_ifval, _LT_SET_OPTIONS, and LT_INIT Platform information: Solaris 10 (sparc) python version 2.4.4, autoconf version 2.63, libtool version 2.2.6b Any idea what [if anything] is causing this? How do I fix it? --Pete
AuthType Certificate integration completed; patch forthcoming
All: I just completed an end-to-end test demonstrating authentication and simple [Require valid-user] authorization mapping an X.509 certificate to an LDAP entry using my new mod_auth_cert module. The module implements AuthType Certificate. I believe the Require ldap-* directives will work as well. (I didn't have to make any changes in the authorization side of mod_authnz_ldap.c.) By extending mod_authnz_ldap, I've avoided the limitations of various 3rd party solutions such as dependence upon specific LDAP schemas. The only requirement my solution imposes is that an attribute in the user's LDAP entry must match the subject of their SSL client certificate. In support of that requirement--at least as implemented in my environment--I'm also adding a new optional flag to mod_ssl that will render the certificate subject in RFC 2253 [XN_FLAGS_RFC2253] format. (By default the current [reversed DN, slash-delimited] rendering of the certificate subject will be used.) I have to go through some machinations to move the patch from my integration test environment out to the Internet for posting to bugzilla. Once I do, I'll at least take a stab at adding documentation and update my existing feature request with the final proposed patch. --Pete
