Bug 2603 - The policy named "maximum password age" now seems to be named "maximum password age (seconds since 1970)" and cannot be read or written to
Summary: The policy named "maximum password age" now seems to be named "maximum passwo...
Alias: None
Product: Samba 3.0
Classification: Unclassified
Component: User/Group Accounts (show other bugs)
Version: 3.0.13
Hardware: x86 Linux
: P3 normal
Target Milestone: none
Assignee: Samba Bugzilla Account
QA Contact: Samba QA Contact
Depends on:
Reported: 2005-04-13 10:11 UTC by Fabio Muzzi Frabetti
Modified: 2005-08-24 10:18 UTC (History)
0 users

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Fabio Muzzi Frabetti 2005-04-13 10:11:31 UTC
Using Samba 3.0.13 (and I believe also 3.0.11 and 3.0.12) when I get a list of
account policies I see that the values "maximum password age" and "minimum
password age" are now called "maximum password age (seconds since 1970)" and
"minimum password age (seconds since 1970)". These two values, that in 3.0.9 had
the correct names (without the "seconds since 1970" part) cannot be read and set

If I try to get the value for "maximum password age" with the command
      pdbedit -P "maximum password age"

I get an error that says:

No account policy by that name
Account policy names are :
min password length
password history
user must logon to change password
maximum password age (seconds since 1970)
minimum password age (seconds since 1970)
lockout duration
reset count minutes
bad lockout attempt
disconnect time
refuse machine password change
If I try then to get the value for "maximum password age (seconds since 1970)"
with the command:

          pdbedit -P "maximum password age (seconds since 1970)"

I get an error that says:

account_policy_get: tdb_fetch_uint32 failed for field 4 (maximum password age
(seconds since 1970)), returning 0
valid account policy, but unable to fetch value!

I get quite the same error if I try to set the value instead of getting it, and
when I create a new user too, I suppose because creating a new user implies
readin the default policy values and adding them to the user's account record (I
use pdb as backend)

The same happens with "minimum password age" policy.
Comment 1 Gerald (Jerry) Carter (dead mail address) 2005-04-13 21:44:07 UTC
Fixed in next stable release (already in SVN).
Comment 2 Gerald (Jerry) Carter (dead mail address) 2005-08-24 10:18:47 UTC
sorry for the same, cleaning up the database to prevent unecessary reopens of bugs.