Ticket History #2625: renew-until 0?, display alignment, redisplay changing config

I just converted MS credentials, and found my creds for
afs/athena.mit.edu have a renew-until time listed of "Dec 31 19:00".
Which usually means there's a zero value in a time field somewhere
which would mean 1/1/1970-0:00 GMT, but normally one would read "Dec"
as meaning the coming (or immediately past, in January) December.
First, zero should probably be treated specially if it can show up
there, as apparently it can; second, if the correct year isn't
intuitive, it should probably be displayed, perhaps instead of the
time if you want to keep things narrow.

And because "Dec" is wider than "Jul", the service principal name
column doesn't line up. That'll probably also come up in real-life
cases with "Jul" versus "Aug" or something.

Destroying and converting again with the old leash executable and DLLs
("Leash Version 2.6.0 (*UNOFFICIAL*)"), and the December date is still
there, so presumably it's in the MS data, or in the MIT-issued
credentials, and not related to the changes I've been making in the
last day or two.

Perhaps a bit more annoying, when the display automatically refreshes
now and then, if I had the enctypes displayed, they go away on
redisplay.

Ken

Please provide a scenario which I can use to produce the 0 renew til
date. What KDC is allowing tickets to be issued with the renewable flag
and a 0 renew-til date?

Regarding the columns, the nodes display single text strings. There is
no ability to adjust the width of columns.


This is by design because there is only so much real estate.

The fact is the entire Leash application needs to be entirely replaced.
I'm looking at the ticket manager window from Wake as a potential jump
start.