Received-SPF: pass (google.com: domain of linux-nfs-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Subject: Re: ksu problem with sec=krb5 and nfs
To:     Benjamin Coddington <bcodding@redhat.com>
Cc:     linux-nfs@vger.kernel.org
References: <abbd93ac-4a68-a471-fbb4-a9baf05b89c9@eecs.yorku.ca>
 <7714ABF4-E9CD-424B-BF7F-6F1B91F58C2B@redhat.com>
From:   Jason Keltz <jas@eecs.yorku.ca>
Message-ID: <dd51738b-b2c2-2dcf-68b1-e78c66d08b28@eecs.yorku.ca>
Date:   Mon, 24 May 2021 10:44:01 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101
 Thunderbird/78.10.1
MIME-Version: 1.0
In-Reply-To: <7714ABF4-E9CD-424B-BF7F-6F1B91F58C2B@redhat.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Precedence: bulk

Hi Benjamin,

That's exactly it - I definately want ksu to be writing that exact 
file.  Any idea why it isn't, and why it matters if the home directory 
is using sec=krb5 or not?

Jason.

On 5/24/2021 7:30 AM, Benjamin Coddington wrote:
> On 22 May 2021, at 10:47, Jason Keltz wrote:
>
>> Can someone help me understand the issue, and whether there is a solution?
> Don't you want ksu to write its target cache to /tmp/krb5cc_1011 so rpc.gssd
> can find it?  Why isn't that happening?
>
> Ben
>
>