[Sam Hartman]
> I suspect it is seconds and I actually like the output in the
> documentation more than the code. So, it might be a better fix to
> update the code to be consistent with the docs.
The manual page should be fixed too. These parts should mention the
unit, or at least refer to valid 'time' notation.
-maxlife time
sets the maximum lifetime of a password
-minlife time
sets the minimum lifetime of a password
Also this section would be be better if it mentioned that the maximum
password life value with the -terse output is in seconds:
get_policy [-terse] policy
displays the values of the named policy. Requires the
inquire privi‐ lege. With the -terse flag, outputs the
fields as quoted strings separated by tabs. Alias getpol.
EXAMPLES:
kadmin: get_policy admin
Policy: admin
Maximum password life: 180 days 00:00:00
Minimum password life: 00:00:00
Minimum password length: 6
Minimum number of password character classes: 2
Number of old keys kept: 5
Reference count: 17
kadmin: get_policy -terse admin
admin 15552000 0 6 2 5 17
kadmin:
> I've confirmed this is a current upstream bug.
> I'll look into fixing it.
Great!
> And yes, it does appear to be seconds.
Thank you!
--
Happy hacking
Petter Reinholdtsen
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
