From bjaspan@MIT.EDU Tue Sep 24 16:20:13 1996
Received: from dragons-lair.MIT.EDU (DRAGONS-LAIR.MIT.EDU [18.177.1.200]) by avalanche-breakdown.MIT.EDU (8.7.5/8.7.3) with SMTP id QAA19938 for <bugs@AVALANCHE-BREAKDOWN.MIT.EDU>; Tue, 24 Sep 1996 16:20:12 -0400
Received: from MIT.EDU (SOUTH-STATION-ANNEX.MIT.EDU [18.72.1.2]) by dragons-lair.MIT.EDU (8.6.13/8.6.9) with SMTP id QAA12935 for <krb5-bugs@dragons-lair.mit.edu>; Tue, 24 Sep 1996 16:20:11 -0400
Received: from DUN-DUN-NOODLES.MIT.EDU by MIT.EDU with SMTP
id AA16251; Tue, 24 Sep 96 16:20:10 EDT
Received: by DUN-DUN-NOODLES.MIT.EDU (5.x/4.7) id AA01251; Tue, 24 Sep 1996 16:20:09 -0400
Message-Id: <9609242020.AA01251@DUN-DUN-NOODLES.MIT.EDU>
Date: Tue, 24 Sep 1996 16:20:09 -0400
From: bjaspan@MIT.EDU
Reply-To: bjaspan@MIT.EDU
To: krb5-bugs@MIT.EDU
Subject: kadmin's getdate is confusing
X-Send-Pr-Version: 3.99
System: SunOS DUN-DUN-NOODLES 5.4 Generic_101945-37 sun4m sparc
kadmin uses getdate to parse dates. The way it handles integers is
very confusing for users. It also happens to parse single letters as
military timezones, so "10h" will parse but mean something very
unexpected. We need to figure out a less confusing solution.
Responsible-Changed-From-To: hartmans->bjaspan
Responsible-Changed-By: bjaspan
Responsible-Changed-When: Tue Sep 24 16:42:08 1996
Responsible-Changed-Why:
From: "Barry Jaspan" <bjaspan@MIT.EDU>
To: gnats@rt-11.MIT.EDU
Cc: Subject: Re: krb5-admin/15: [rsalz@osf.org: Re: maxlife (was Re: Bug fix: kdc.conf not being read)]
Date: Thu, 26 Sep 1996 15:52:30 -0400
From: Rich Salz <rsalz@osf.org>
Date: Thu, 26 Sep 1996 15:49:10 -0400
To: bjaspan@MIT.EDU
Subject: Re: maxlife (was Re: Bug fix: kdc.conf not being read)
The problem is relative dates. Snarf the getdate.y from INN if you
want a stripped-down version. Or I could give you something that
only took relative dates. Or, snarf the sendmail "10h30m" time parser.
From: "Barry Jaspan" <bjaspan@MIT.EDU>
To: bjaspan@MIT.EDU
Cc: krb5-bugs@MIT.EDU
Subject: Re: krb5-admin/15: kadmin's getdate is confusing
Date: Tue, 8 Oct 1996 17:55:17 -0400
Another way that getdate is confusing is that if you enter an absolute
date, such as "11/30/96", DST changes are applied so that the actual
value that gets set may be, for example, 11pm 11/29/96. Example:
kadmin.local: modprinc -pwexpire "11/30/96" testuser
Principal "testuser@SECURE-TEST.OV.COM" modified.
kadmin.local: getprinc testuser
Principal: testuser@SECURE-TEST.OV.COM
Expiration date: Tue Dec 31 23:00:00 EST 1996
Last password change: Tue Oct 08 11:49:38 EDT 1996
Password expiration date: Fri Nov 29 23:00:00 EST 1996
[ remainder deleted ]
From: "Barry Jaspan" <bjaspan@MIT.EDU>
To: bjaspan@MIT.EDU
Cc: krb5-bugs@MIT.EDU
Subject: Re: krb5-admin/15: kadmin's getdate is confusing
Date: Fri, 18 Oct 1996 13:49:27 -0400
I checked in a change to getdate.y to make it less confusing. Plain
integers are no longer accepted as a date specifiction, and military
time zones (a-z) are no longer recognized (otherwise something like
"10h" is parsed but means something very unexpected).
I'm not sure this is the final solution to the problem, though.
From: "Theodore Y. Ts'o" <tytso@MIT.EDU>
To: Barry Jaspan <bjaspan@MIT.EDU>
Cc: krb5-bugs@MIT.EDU
Subject: Re: krb5-admin/15: kadmin's getdate is confusing
Date: Mon, 4 Nov 1996 14:38:03 -0500
`Theodore Y. Ts'o' made changes to this PR.
*** /tmp/gnatsa002kB Mon Nov 4 14:35:57 1996
--- /tmp/gnatsb002kB Mon Nov 4 14:37:38 1996
***************
*** 17,23 ****
Per meeting on Friday.
Responsible-Changed-From-To: bjaspan->krb5-unassigned
Responsible-Changed-By: mdh
Responsible-Changed-When: Tue Jun 23 21:49:53 1998
Responsible-Changed-Why:
bjaspan no longer works on kerberos
Received: from dragons-lair.MIT.EDU (DRAGONS-LAIR.MIT.EDU [18.177.1.200]) by avalanche-breakdown.MIT.EDU (8.7.5/8.7.3) with SMTP id QAA19938 for <bugs@AVALANCHE-BREAKDOWN.MIT.EDU>; Tue, 24 Sep 1996 16:20:12 -0400
Received: from MIT.EDU (SOUTH-STATION-ANNEX.MIT.EDU [18.72.1.2]) by dragons-lair.MIT.EDU (8.6.13/8.6.9) with SMTP id QAA12935 for <krb5-bugs@dragons-lair.mit.edu>; Tue, 24 Sep 1996 16:20:11 -0400
Received: from DUN-DUN-NOODLES.MIT.EDU by MIT.EDU with SMTP
id AA16251; Tue, 24 Sep 96 16:20:10 EDT
Received: by DUN-DUN-NOODLES.MIT.EDU (5.x/4.7) id AA01251; Tue, 24 Sep 1996 16:20:09 -0400
Message-Id: <9609242020.AA01251@DUN-DUN-NOODLES.MIT.EDU>
Date: Tue, 24 Sep 1996 16:20:09 -0400
From: bjaspan@MIT.EDU
Reply-To: bjaspan@MIT.EDU
To: krb5-bugs@MIT.EDU
Subject: kadmin's getdate is confusing
X-Send-Pr-Version: 3.99
Show quoted text
>Number: 15
>Category: krb5-admin
>Synopsis: kadmin's getdate is confusing
>Confidential: no
>Severity: serious
>Priority: low
>Responsible: krb5-unassigned
>State: open
>Class: sw-bug
>Submitter-Id: unknown
>Arrival-Date: Tue Sep e 16:25:01 EDT 1996
>Last-Modified: Tue Jun 23 21:52:29 EDT 1998
>Originator: Barry Jaspan
>Organization:
mit>Category: krb5-admin
>Synopsis: kadmin's getdate is confusing
>Confidential: no
>Severity: serious
>Priority: low
>Responsible: krb5-unassigned
>State: open
>Class: sw-bug
>Submitter-Id: unknown
>Arrival-Date: Tue Sep e 16:25:01 EDT 1996
>Last-Modified: Tue Jun 23 21:52:29 EDT 1998
>Originator: Barry Jaspan
>Organization:
Show quoted text
>Release: unknown-1.0
>Environment:
>Environment:
System: SunOS DUN-DUN-NOODLES 5.4 Generic_101945-37 sun4m sparc
Show quoted text
>Description:
kadmin uses getdate to parse dates. The way it handles integers is
very confusing for users. It also happens to parse single letters as
military timezones, so "10h" will parse but mean something very
unexpected. We need to figure out a less confusing solution.
Show quoted text
>How-To-Repeat:
Show quoted text
>Fix:
Show quoted text
>Audit-Trail:
Responsible-Changed-From-To: hartmans->bjaspan
Responsible-Changed-By: bjaspan
Responsible-Changed-When: Tue Sep 24 16:42:08 1996
Responsible-Changed-Why:
From: "Barry Jaspan" <bjaspan@MIT.EDU>
To: gnats@rt-11.MIT.EDU
Cc: Subject: Re: krb5-admin/15: [rsalz@osf.org: Re: maxlife (was Re: Bug fix: kdc.conf not being read)]
Date: Thu, 26 Sep 1996 15:52:30 -0400
From: Rich Salz <rsalz@osf.org>
Date: Thu, 26 Sep 1996 15:49:10 -0400
To: bjaspan@MIT.EDU
Subject: Re: maxlife (was Re: Bug fix: kdc.conf not being read)
The problem is relative dates. Snarf the getdate.y from INN if you
want a stripped-down version. Or I could give you something that
only took relative dates. Or, snarf the sendmail "10h30m" time parser.
From: "Barry Jaspan" <bjaspan@MIT.EDU>
To: bjaspan@MIT.EDU
Cc: krb5-bugs@MIT.EDU
Subject: Re: krb5-admin/15: kadmin's getdate is confusing
Date: Tue, 8 Oct 1996 17:55:17 -0400
Another way that getdate is confusing is that if you enter an absolute
date, such as "11/30/96", DST changes are applied so that the actual
value that gets set may be, for example, 11pm 11/29/96. Example:
kadmin.local: modprinc -pwexpire "11/30/96" testuser
Principal "testuser@SECURE-TEST.OV.COM" modified.
kadmin.local: getprinc testuser
Principal: testuser@SECURE-TEST.OV.COM
Expiration date: Tue Dec 31 23:00:00 EST 1996
Last password change: Tue Oct 08 11:49:38 EDT 1996
Password expiration date: Fri Nov 29 23:00:00 EST 1996
[ remainder deleted ]
From: "Barry Jaspan" <bjaspan@MIT.EDU>
To: bjaspan@MIT.EDU
Cc: krb5-bugs@MIT.EDU
Subject: Re: krb5-admin/15: kadmin's getdate is confusing
Date: Fri, 18 Oct 1996 13:49:27 -0400
I checked in a change to getdate.y to make it less confusing. Plain
integers are no longer accepted as a date specifiction, and military
time zones (a-z) are no longer recognized (otherwise something like
"10h" is parsed but means something very unexpected).
I'm not sure this is the final solution to the problem, though.
From: "Theodore Y. Ts'o" <tytso@MIT.EDU>
To: Barry Jaspan <bjaspan@MIT.EDU>
Cc: krb5-bugs@MIT.EDU
Subject: Re: krb5-admin/15: kadmin's getdate is confusing
Date: Mon, 4 Nov 1996 14:38:03 -0500
`Theodore Y. Ts'o' made changes to this PR.
*** /tmp/gnatsa002kB Mon Nov 4 14:35:57 1996
--- /tmp/gnatsb002kB Mon Nov 4 14:37:38 1996
***************
*** 17,23 ****
Show quoted text
>Synopsis: kadmin's getdate is confusing
>Confidential: no
>Severity: serious
! >Priority: medium>Confidential: no
>Severity: serious
Show quoted text
>Responsible: bjaspan
>State: open
>Class: sw-bug
--- 17,23 ---->State: open
>Class: sw-bug
Show quoted text
>Synopsis: kadmin's getdate is confusing
>Confidential: no
>Severity: serious
! >Priority: low>Confidential: no
>Severity: serious
Show quoted text
>Responsible: bjaspan
>State: open
>Class: sw-bug
>State: open
>Class: sw-bug
Per meeting on Friday.
Responsible-Changed-From-To: bjaspan->krb5-unassigned
Responsible-Changed-By: mdh
Responsible-Changed-When: Tue Jun 23 21:49:53 1998
Responsible-Changed-Why:
bjaspan no longer works on kerberos
Show quoted text
>Unformatted: