[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: (ITS#3737) Patch to passwd backend

I am reluctant to adapt back-passwd into something useful
beyond its primary use as a example of how a backend
interfaces with the frontend as that will distract from
an example.  In fact, I recall purposely avoiding using
account and/or posixAccount schema when updating back-passwd
some years ago.  (I vaguely recall receiving and rejecting
a similar patch years ago as well.)

I also note that if one were to redesign back-passwd
for other uses, back-passwd suffers from numerous problems
which make it inappropriate for use any many environments.
For instance, the backend serializes search operations.
It doesn't even take advantage of setpassent(3).  And
some form of caching would be wise.   However, addressing
this issues in back-passwd would, I think, distract from
the primary purpose of back-passwd, to be an example.

Hence, I think any development of a "real" passwd backend
should be done separate from this example backend.

Anyways, I am open to more discussion here...  I just wanted
to inject some history and personal thoughts into the


At 11:26 PM 5/19/2005, daveh@ci.com.au wrote:
>Full_Name: Dave Horsfall
>Version: 2.2.26
>OS: FreeBSD 4.10-STABLE
>URL: ftp://ftp.openldap.org/incoming/dave-horsfall-050520.patch
>Submission from: (NULL) (
>It turns out we have a use for the "passwd" backend, once it was modified,
>This patch changes the backend to return an account/posixAccount object
>(formerly person/uidObject) with the appropriate attributes.
>I, Dave Horsfall, hereby place the following modifications to OpenLDAP Software
>(and only these modifications) into the public domain. Hence, these
>modifications may be freely used and/or redistributed for any purpose with or
>without attribution and/or other notice.