| From: | petesea@bigfoot.com |
| Date: | Sat, 26 Aug 2006 10:49:40 -0700 (Pacific Daylight Time) |
| Subject: | kadmin: password expiration date format |
| To: | kfw-bugs@mit.edu |
Using krb5-1.4.3.
Is there any chance the admin internal help or kadmin error message could
be enhanced to include the format of an acceptable password expiration
date.
I'm forever forgetting the format required to set an expiration date and
the only message I get back is a "kick me while I'm down" error:
Invalid date specification "8/21/06"
That doesn't really help much.. how about saying what the specification
SHOULD be. :-)
And by the way... with all the formats that ARE accepted, why isn't
"mm/dd/yy" valid. Is it because of the ambiguity between the US and "the
rest of the world"... in other words "mm/dd/yy" vs "dd/mm/yy"? If that's
the case, then why is "dd/mm/yy HH:MM:SS TZ" accepted?.. actually it
doesn't look like that works either... despite what the man page says.
Is there any chance the admin internal help or kadmin error message could
be enhanced to include the format of an acceptable password expiration
date.
I'm forever forgetting the format required to set an expiration date and
the only message I get back is a "kick me while I'm down" error:
Invalid date specification "8/21/06"
That doesn't really help much.. how about saying what the specification
SHOULD be. :-)
And by the way... with all the formats that ARE accepted, why isn't
"mm/dd/yy" valid. Is it because of the ambiguity between the US and "the
rest of the world"... in other words "mm/dd/yy" vs "dd/mm/yy"? If that's
the case, then why is "dd/mm/yy HH:MM:SS TZ" accepted?.. actually it
doesn't look like that works either... despite what the man page says.