(root)/head : changes from revision 41

From Revision 41 to 22

Rev	Summary	Authors	Date	Diff	Files
41	- update syntax for multiple hosts - update syntax for multiple hosts - mention that multiple urls are now supported - LDAPUserDirUseTLS enables TLS not SSL	John Morrissey	2009-11-27
40	prep for 1.1.17 release prep for 1.1.17 release	John Morrissey	2009-11-24
39	actually, we don't have to pass LDAPUserDir{,URL} arguments ... actually, we don't have to pass LDAPUserDir{,URL} arguments through ap_getword_conf, just LDAPUserDirServer, to break any space-separated hosts up so we can iterate through them ourselves.	John Morrissey	2009-11-24
38	ned to call ap_getword_conf() to break args up (for example,... ned to call ap_getword_conf() to break args up (for example, so we get individual LDAP servers and can iterate over them ourselves instead of passing the whole space-separated arg to the LDAP SDK) and dispel any quoting.	John Morrissey	2009-11-24
37	mention using "." to have the home directory itself be apach... mention using "." to have the home directory itself be apache-accessible. thanks to Peter Tselios <tselios.petros@gmail.com> for mentioning this.	John Morrissey	2009-11-24
36	- the handler for LDAPUserDir doesn't need to take raw args;... - the handler for LDAPUserDir doesn't need to take raw args; use ITERATE instead. - fix apache 1.3.x incompatibility that snuck in when adding array manipulation	John Morrissey	2009-11-24
35	mention that './configure --help' provides information on bu... mention that './configure --help' provides information on build options	John Morrissey	2009-11-24
34	fix LDAP server failover by implementing our own failover me... fix LDAP server failover by implementing our own failover mechanism instead of relying on the LDAP SDK's. ldap server failover (space-separated list of hostnames in the argument to LDAPServer) has been broken since 1.1.13 when ldap_init() was replaced with ldap_initialize(), if available. as of that commit, a LDAP URL is constructed if simple hostname(s) are passed to LDAPServer, so: 'LDAPServer "127.0.0.1 172.16.0.5" was passed to ldap_initailize() as: ldap://127.0.0.1 172.16.0.5/ Unfortunately, ldap_url_parse() treats this as a valid URL, but ldap_intiailize() will not fail over to subsequent LDAP servers should the first be unreachable. ldap_initialize() will take a whitespace-separated list of LDAP URLs and will fail over successfully, just not when whitespace-separated hostname are passed to a single url (even if the whitespace in the hostname portion of the URL is urlencoded as %20). Also, mod_ldap_userdir wouldn't accept multiple LDAP URLs passed to LDAPServerURL, so failover wasn't possible when specifying URLs. forget all of this SDK-based failover and implement our own failover support, since afaict Sun's ancient LDAP SDK doesn't implement failover and it's nice to be able to control it ourselves. for that matter, we need to control it ourselves since we need to use the URL parameters (base DN, filter, search scope) indicated by the URL at hand. chances are, these items will be the same for all URLs passed to LDAPServer, but to be completely correct, we should use the scope corresponding to the current URL and ldap_initialize() provides no way to tell what URL it wound up connecting to.	John Morrissey	2009-11-24
33	update version update version	John Morrissey	2009-11-20
32	more generic ldif example more generic ldif example	John Morrissey	2009-06-20
31	remove ancient objectclass definition remove ancient objectclass definition	John Morrissey	2009-04-03
30	v1.1.16: v1.1.16: * TLS support was not being enabled when the --with-tls option was explicitly passed to configure. Replace --with-tls with the more correct option --enable-tls.	John Morrissey	2009-04-03
29	v1.1.15: v1.1.15: * Fix segfault when LDAPUserDirDNInfo isn't specified (implicitly specifying anonymous binds) with modern LDAP SDKs (LDAP_API_VERSION >= 2000).	John Morrissey	2009-03-16
28	v1.1.14: v1.1.14: * Avoid segfault attempting to free() uninitialized pointer when a user does not have a uid or homeDirectory attr, one or both of those attrs are not readable by the DN configured by LDAPUserDirDNInfo, or an out-of-memory condition is encountered while fetching any LDAP attribute.	John Morrissey	2008-10-09
27	update docs to reflect need to urlencoding in LDAP URLs update docs to reflect need to urlencoding in LDAP URLs	John Morrissey	2008-10-08
26	release 1.1.13 release 1.1.13	John Morrissey	2008-10-08
25	v1.1.13-20081008: v1.1.13-20081008: * Avoid infinite loop when LDAPUserDirDNInfo bind DN doesn't have access to one or more LDAP attributes. * Logging improvements * Don't complain about inaccessible [ug]idNumber values when reading the user's LDAP entry, since we might not be using suexec. * Complain in suexec handler if we found the user's LDAP entry but it was missing [ug]idNumber values.	John Morrissey	2008-10-08
24	remove debugging cruft remove debugging cruft	John Morrissey	2008-10-07
23	* Fixes to bugs in suexec support submitted by Witold Barylu... * Fixes to bugs in suexec support submitted by Witold Baryluk <baryluk@smp.if.uj.edu.pl>.	John Morrissey	2008-10-07
22	1.1.13-20081007: 1.1.13-20081007: * Missed ldap_init() -> ldap_initialize() change when making changes to comply with draft-ietf-ldapext-ldap-c-api-04. Older versions may segfault on 64-bit systems when mod_ldap_userdir is built with more recent OpenLDAP SDK headers. * Previous versions enabled TLS when the ldaps:// scheme was specified in LDAPUserdirServerURL URL. This behavior was incorrect, since ldaps:// indicates LDAP over SSL (port 636 by default) should be enabled. If you wish to continue using TLS, you must modify your configuration to specify the ldap:// scheme in the LDAPUserdirServerURL URL and add the directive 'LDAPUserDirUseTLS on' to your configuration. * LDAPUserDirUseTLS now throws a configuration error when TLS is enabled and the ldaps:// scheme is specified in the LDAPUserdirServerURL URL.	John Morrissey	2008-10-07

Older

Loggerhead 1.17 is a web-based interface for Bazaar branches