CVS update: samba/source/nsswitch

Luke Howard lukeh at PADL.COM
Wed Mar 24 20:44:16 GMT 2004

Not sure to what extent you are using GSS-API, but you might like
to check for and use if present gss_krb5_ccache_name().

-- Luke

>From: Jeremy Allison <jra at>
>Subject: Re: CVS update: samba/source/nsswitch
>To: Jim McDonough <jmcd at>
>Cc: samba-technical at, jmcd at, Jeremy Allison <jra at>
>Date: Wed, 24 Mar 2004 12:15:11 -0800
>On Wed, Mar 24, 2004 at 02:10:37PM -0500, Jim McDonough wrote:
>> >Is this ccache name :
>> >
>> >+ ads_kdestroy("MEMORY:winbind_ccache");
>> >
>> >Portable.... I don't think so ? (Can't check now sorry).
>> Hmm, seems we're already in trouble if it isn'  or does
>> setenv("KRB5CCNAME", "MEMORY:winbind_ccache", 1) not cause the same
>> problem?
>> Do you suggest I just do the same setenv above, and call ads_kdestroy with
>> no name(basically, take the default ccache) ?
>Hmmm. Looking at the code now it seems like MEMORY:xxx_Cache
>setenv calls have proliferated like rabbits :-).
>libsmb/cliconnect.c:    setenv(KRB5_ENV_CCNAME, "MEMORY:cliconnect", 1);
>nsswitch/winbindd_ads.c:setenv("KRB5CCNAME", "MEMORY:winbind_ccache", 1);
>printing/nt_printing.c: setenv(KRB5_ENV_CCNAME, "MEMORY:prtpub_cache", 1);
>printing/nt_printing.c: setenv(KRB5_ENV_CCNAME, "MEMORY:prtpub_cache", 1);
>utils/net_ads.c:        setenv(KRB5_ENV_CCNAME, "MEMORY:net_ads", 1);
>So I guess doing the setenv way seems to be the way we're
>already doing it :-).

More information about the samba-technical mailing list