[31237] in Kerberos
Re: Logging on with cached ticket
daemon@ATHENA.MIT.EDU (Russ Allbery)
Fri Jun 5 11:30:36 2009
To: Nikolay Shopik <shopik@inblock.ru>
In-Reply-To: <4A29322D.6030707@inblock.ru> (Nikolay Shopik's message of "Fri\,
05 Jun 2009 18\:56\:45 +0400")
From: Russ Allbery <rra@stanford.edu>
Date: Fri, 05 Jun 2009 08:29:59 -0700
Message-ID: <87oct266mg.fsf@windlord.stanford.edu>
MIME-Version: 1.0
Cc: kerberos@mit.edu
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: kerberos-bounces@mit.edu
Nikolay Shopik <shopik@inblock.ru> writes:
> On 05.06.2009 18:36, Russ Allbery wrote:
>> Nikolay Shopik<shopik@inblock.ru> writes:
>>> Only thing I found is pam_krb5 which have existing_ticket
>>> option. (tells pam_krb5.so to accept the presence of pre-existing
>>> Kerberos credentials provided by the calling application in the
>>> default credential cache as sufficient to authenticate the user, and
>>> to skip any account management checks). While this available only in
>>> Red Hat from what I see but not in Debian/Ubuntu.
>> I could add it easily enough. I just never understood the use case.
>> Could you explain more about how you end up in this situation? Where
>> is the ticket coming from that's being used for authentication?
> Option "existing_ticket" not available on Debian libpam-krb5
> package. I'm sorry which situation exactly?
Why would you ever want that option? What's the point of it?
> Well ticket is coming from KDC when it was available and can be used
> until it expired, from my understanding.
Sure, but how come you're running through a PAM stack that cares about
your existing ticket when you still have a ticket available? There's
probably some obvious case where this happens; I just don't know what it
is.
--
Russ Allbery (rra@stanford.edu) <http://www.eyrie.org/~eagle/>
________________________________________________
Kerberos mailing list Kerberos@mit.edu
https://mailman.mit.edu/mailman/listinfo/kerberos
