[35820] in Kerberos
Re: On credential cache separation between service ticket and TGT
daemon@ATHENA.MIT.EDU (Greg Hudson)
Wed Mar 5 10:29:45 2014
Message-ID: <531742C7.4040101@mit.edu>
Date: Wed, 05 Mar 2014 10:29:11 -0500
From: Greg Hudson <ghudson@mit.edu>
MIME-Version: 1.0
To: Arpit Srivastava <arpit.orb@gmail.com>, kerberos <kerberos@mit.edu>
In-Reply-To: <CAEvOXU4MDL99atB=ieOw3u+Kvwkg9kKeS7vExV0sqxu9CDUZ7A@mail.gmail.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: kerberos-bounces@mit.edu
On 03/05/2014 09:43 AM, Arpit Srivastava wrote:
> 1. Is there any way to selectively expose service ticket and not the
> TGT to the applications (which will be using GSS APIs) ? Can we store both
> of them in different files and not together in single krb5cc ?
You could copy the service ticket into a different ccache and expose
only that to the application. GSSAPI applications will work fine if
they have a service ticket and no TGT.
There are no GSS functions for doing this kind of selective copying; you
would have to use ccache functions from libkrb5, or use kinit -S (or
equivalent) to avoid getting a TGT in the first place.
> 2. If I give away the krb5cc ( which also contains TGT) to the
> application, Can application make use (for eg. obtaining service tickets
> for other SPNs for malicious purposes) of its TGT part after calling
> acquire_cred or any other API ?
Yes, if you expose a TGT to an application then it could use that to
obtain any service ticket.
________________________________________________
Kerberos mailing list Kerberos@mit.edu
https://mailman.mit.edu/mailman/listinfo/kerberos
