linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Doug Nazar <nazard@nazar.ca>
To: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: gssd keytab resolution
Date: Wed, 1 Jul 2020 17:57:11 -0400	[thread overview]
Message-ID: <487c34e4-1ba3-a77f-3257-c47cdc6c6a1c@nazar.ca> (raw)
In-Reply-To: <e61057cc-6c4b-6d88-aab2-c5d5db9bdf50@nazar.ca>

On 2020-06-29 10:57, Doug Nazar wrote:
> While playing around I noticed this pattern occasionally.
>
> I was wondering if 'srchost=*' should be treated as NULL (use 
> gethostname) or to just skip the loop where we call 
> krb5_kt_get_entry() since that won't match with an asterisk.

Nope, looks like this was me. During a rebase I managed to get 
gssd_proc.c compiled with the old version of krb5_util.h and gentoo 
disables dependency tracking by default.

Seems to have gone away now after a make clean, was able to reproduce it 
for hours... sigh.

So, that patch can be dropped.

Doug


      reply	other threads:[~2020-07-01 21:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-29 14:57 gssd keytab resolution Doug Nazar
2020-07-01 21:57 ` Doug Nazar [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=487c34e4-1ba3-a77f-3257-c47cdc6c6a1c@nazar.ca \
    --to=nazard@nazar.ca \
    --cc=linux-nfs@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).