[28967] in Kerberos
Re: Tickets Longer Than Wanted?
daemon@ATHENA.MIT.EDU (John Hascall)
Fri Jan 4 17:48:09 2008
To: Tom Yu <tlyu@mit.edu>
In-reply-to: Your message of Fri, 04 Jan 2008 17:32:43 -0500.
<ldvlk752pdg.fsf@cathode-dark-space.mit.edu>
Date: Fri, 04 Jan 2008 16:47:16 CST
Message-ID: <17517.1199486836@malison.ait.iastate.edu>
From: John Hascall <john@iastate.edu>
Cc: kerberos@mit.edu
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: kerberos-bounces@mit.edu
> >>>>> "John" == John Hascall <john@iastate.edu> writes:
> John> Given the following code snippet:
>
> krb5_creds rq;
> time_t now = time(NULL);
> memset(&rq, 0, sizeof(rq));
> rq.times.starttime = now;
> rq.times.endtime = now + 1024;
> rq.client = iasc->sc_k5_me;
> rq.server = server;
> k5_err = krb5_get_in_tkt_with_keytab(iasc->sc_k5_context, 0,
> NULL, NULL, NULL,
> iasc-sc_k5_keytab,
> NULL, &rq, NULL);
>
> John> Why am I getting tickets with a 1 day (86400 second) lifetime?
> John> (I was trying to test with a short lifetime to see if some
> John> ticket-renewing code was working correctly and waiting a day
> John> to do each test is hopeless).
>
> The krb5_get_in_tkt functions are deprecated; please use
> krb5_get_init_creds functions instead.
That seems to work.
> Also, what release are you
> running? ... bug in krb5-1.3 ...
> If you are seeing this behavior with a recent release, we would
> appreciate hearing more details.
1.6.3
Thanks,
John
PS, Is there going to be an upto date API document at some point?
________________________________________________
Kerberos mailing list Kerberos@mit.edu
https://mailman.mit.edu/mailman/listinfo/kerberos
