Kerberos for Windows 2.6.5 ccname FILE: issues - Kerberos

This is a discussion on Kerberos for Windows 2.6.5 ccname FILE: issues - Kerberos ; I have found these problems when running Kerberos for Windows 2.6.5: When I use the environment variable %KRB5CCNAME% and set it to "FILE:c:\temp\krbcache" without the quotes it works fine. Leash is able to create and renew, but uses 100% CPU ...

+ Reply to Thread
Results 1 to 2 of 2

Thread: Kerberos for Windows 2.6.5 ccname FILE: issues

  1. Kerberos for Windows 2.6.5 ccname FILE: issues

    I have found these problems when running Kerberos for Windows 2.6.5:

    When I use the environment variable %KRB5CCNAME% and set it to
    "FILE:c:\temp\krbcache" without the quotes it works fine. Leash is
    able to create and renew, but uses 100% CPU time when I try to destroy
    the ticket.

    Also kdestoy.exe does not destroy the ticket and also fails giving an
    error message

    "kdestroy: No credentials cache found while destroying cache"

    When I use the registry key
    "HKEY_LOCAL_MACHINE\SOFTWARE\MIT\kerberos5,cnname" to
    "FILE:c:\temp\krbcache"

    Again Leash is able to create and renew, but it uses 100% CPU when you
    try to destroy the ticket. However, kdestroy is able to destory the
    ticket using this method.

    Is there any way to get Leash to destory this ticket when using the
    FILE:c:\temp\krbcache?

    Thanks

    Noah Hughes

    ________________________________________________
    Kerberos mailing list Kerberos@mit.edu
    https://mailman.mit.edu/mailman/listinfo/kerberos


  2. Re: Kerberos for Windows 2.6.5 ccname FILE: issues

    Noah:

    Can you provide any additional information that might be used to
    replicate the problem?

    I'm using Windows XP SP2:

    [C:\src\openafs\openafs-cvs\src\WINNT\afsd]set
    KRB5CCNAME=FILE:c:\temp\krbcache

    [C:\src\openafs\openafs-cvs\src\WINNT\afsd]kinit jaltman@ATHENA.MIT.EDU
    Password for jaltman@ATHENA.MIT.EDU:

    [C:\src\openafs\openafs-cvs\src\WINNT\afsd]kvno
    afs/athena.mit.edu@ATHENA.MIT.EDU
    afs/athena.mit.edu@ATHENA.MIT.EDU: kvno = 3

    [C:\src\openafs\openafs-cvs\src\WINNT\afsd]klist
    Ticket cache: FILE:c:\temp\krbcache
    Default principal: jaltman@ATHENA.MIT.EDU

    Valid starting Expires Service principal
    07/15/05 17:42:38 07/16/05 03:42:39 krbtgt/ATHENA.MIT.EDU@ATHENA.MIT.EDU
    07/15/05 17:42:55 07/16/05 03:42:39 afs/athena.mit.edu@ATHENA.MIT.EDU


    Kerberos 4 ticket cache: API:krb4cc
    Principal: jaltman@ATHENA.MIT.EDU

    Issued Expires Principal
    07/15/05 17:37:39 07/16/05 03:42:39 krbtgt.ATHENA.MIT.EDU@ATHENA.MIT.EDU

    [C:\src\openafs\openafs-cvs\src\WINNT\afsd]kdestroy

    [C:\src\openafs\openafs-cvs\src\WINNT\afsd]klist
    klist.exe: No credentials cache found (ticket cache FILE:c:\temp\krbcache)


    Kerberos 4 ticket cache: API:krb4cc
    klist.exe: No ticket file (tf_util)

    Jeffrey Altman


    Noah Hughes wrote:

    > I have found these problems when running Kerberos for Windows 2.6.5:
    >
    > When I use the environment variable %KRB5CCNAME% and set it to
    > "FILE:c:\temp\krbcache" without the quotes it works fine. Leash is
    > able to create and renew, but uses 100% CPU time when I try to destroy
    > the ticket.
    >
    > Also kdestoy.exe does not destroy the ticket and also fails giving an
    > error message
    >
    > "kdestroy: No credentials cache found while destroying cache"
    >
    > When I use the registry key
    > "HKEY_LOCAL_MACHINE\SOFTWARE\MIT\kerberos5,cnname" to
    > "FILE:c:\temp\krbcache"
    >
    > Again Leash is able to create and renew, but it uses 100% CPU when you
    > try to destroy the ticket. However, kdestroy is able to destory the
    > ticket using this method.
    >
    > Is there any way to get Leash to destory this ticket when using the
    > FILE:c:\temp\krbcache?
    >
    > Thanks
    >
    > Noah Hughes
    >
    > ________________________________________________
    > Kerberos mailing list Kerberos@mit.edu
    > https://mailman.mit.edu/mailman/listinfo/kerberos
    >


    --
    -----------------
    This e-mail account is not read on a regular basis.
    Please send private responses to jaltman at mit dot edu

+ Reply to Thread