Your message dated Tue, 13 May 2014 13:43:21 -0700
with message-id
<camxh3qbaacwjmqu0rnaavgxhx5_0-8e2pz_cgk+m9dbopc6...@mail.gmail.com>
and subject line operational attrs already present in ppolicy.c
has caused the Debian Bug report #680049,
regarding Old version of ppolicy.schema included
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
680049: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680049
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: slapd
Version: 2.4.23-7.2
Severity: normal
The file /etc/ldap/schema/ppolicy.schema included with the package is
version "1.2.2.4 2007/01/02", while the version included with the
"official" tarball of openldap-2.4.23 is 1.7.2.5 2010/04/13. Curiously,
there is no ppolicy.schema at all in the .orig.tar.gz of the debian package.
The newer version included several added attributes (PWDCHANGEDTIME,
PWDHISTORY, PWDFAILURETIME, PWDGRACEUSETIME) which are needed e.g. by GoSA.
--- End Message ---
--- Begin Message ---
Hi,
As Quanah wrote, there's no need for the mentioned attributes
(pwdChangedTime, pwdHistory, pwdFailureTime, pwdGraceUseTime) to be
included in the schema, because they're operational attributes defined
directly in the ppolicy module.
I confirm that in squeeze (and later), after loading the ppolicy
module and schema (as provided in the package), adding the overlay,
and changing a user's password with ldappasswd(1), the pwdChangedTime
attribute appears and works as expected; and after a failed bind the
pwdFailureTime attribute appears and works as expected.
I concur with Brian that there is no functional difference between the
upstream ppolicy.schema and Debian's, and therefore close this bug.
thanks,
Ryan
--- End Message ---
