🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Thread View: comp.protocols.kerberos
2 messages
2 total messages Started by Jonathan I. Kamens Wed, 16 Dec 1992 14:15
V5 equivalent of KRBTKFILE
#840
Author: Jonathan I. Kamens
Date: Wed, 16 Dec 1992 14:15
13 lines
967 bytes
In the MIT V5 distribution, is there an application-transparent way to tell the
Kerberos libraries to use a different ticket cache, i.e., something equivalent
to what KRBTKFILE does in V4?

I did some source digging and couldn't find anything.  Did I miss it, or is it
not there?  If the latter, are there any plans to add something like this, and
if so, have the details been codified?

Thanks,

-- 
Jonathan Kamens                                         jik@MIT.Edu
MIT Information Systems/Athena              Moderator, news.answers
Re: V5 equivalent of KRBTKFILE
#842
Author: Steve Dyer
Date: Wed, 16 Dec 1992 16:00
26 lines
1453 bytes
In article <1gndmfINN6d3@senator-bedfellow.MIT.EDU> jik@athena.mit.edu (Jonathan I. Kamens) writes:
>In the MIT V5 distribution, is there an application-transparent way to tell the
>Kerberos libraries to use a different ticket cache, i.e., something equivalent
>to what KRBTKFILE does in V4?

/*
 * This file contains the source code for krb5_fcc_default_name.
 * 
 * Effects:
 * 
 * Forms the default credential cache name for the current user, which
 * is defined in the following way.  If it is set, the environment
 * variable "KRB5CCACHE" will be used (up to the maximum number of
 * characters of a legal operating system defined path).  Otherwise
 * TKT_ROOT (from fcc.h) and the user's uid are concatenated to
 * produce the ticket file name (e.g., "/tmp/tkt123").  The pointer
 * returned is to static storage; the name must be copied elsewhere.
 */

char *
krb5_fcc_default_name ()
{ ... }

-- 
Steve Dyer
dyer@ursa-major.spdcc.com aka {ima,harvard,rayssd,linus,m2c}!spdcc!dyer
Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads