> On Jul 17, 2015, at 9:13 AM, Simo Sorce wrote:
>
> - Original Message -
>> From: "John Devitofranceschi"
>>
>> How long does it take for the stored session keys to expire after the ccache
>> is destroyed? Is it based on ticket lifetime?
>
> Yes, the "endtime" of the established con
- Original Message -
> From: "John Devitofranceschi"
> To: kerberos@mit.edu
> Cc: "Simo Sorce"
> Sent: Friday, July 17, 2015 6:52:01 AM
> Subject: Re: kerberos ticket cache
>
>
> > On Jul 10, 2015, at 10:06 AM, Simo Sorce wrote:
> &
> On Jul 10, 2015, at 10:06 AM, Simo Sorce wrote:
>
>
> The same is for Kerberized NFS in Linux, the session keys are stored in
> the kernel and there is currently no way to revoke them, however once
> the session is destroyed the kernel will not be able to recreate it.
>
How long does it ta
On Fri, 2015-07-10 at 09:52 -0400, Tom Yu wrote:
> Andrew Levin writes:
>
> > I have noticed that even after I delete my kerberos ticket cache, as below,
> > I remain authenticated (eg I can open files in an area where kerberos
> > authentication is required). How is this possible?
> >
> > [anl
On Fri, 2015-07-10 at 08:37 +, Andrew Levin wrote:
> I have noticed that even after I delete my kerberos ticket cache, as
> below, I remain authenticated (eg I can open files in an area where
> kerberos authentication is required). How is this possible?
There is a procedure called "aklog" whic
Andrew Levin writes:
> I have noticed that even after I delete my kerberos ticket cache, as below, I
> remain authenticated (eg I can open files in an area where kerberos
> authentication is required). How is this possible?
>
> [anlevin@lxplus0055 ~]$ klist
> Ticket cache: FILE:/tmp/krb5cc_1353
Does the same happen with kdestroy? Looks like an internal caching issue.
Have you tried calling sync?
On Jul 10, 2015 9:42 AM, "Andrew Levin" wrote:
> Hi,
>
> I have noticed that even after I delete my kerberos ticket cache, as
> below, I remain authenticated (eg I can open files in an area whe
