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: gssd keytab resolution
Date: Mon, 29 Jun 2020 10:57:31 -0400	[thread overview]
Message-ID: <e61057cc-6c4b-6d88-aab2-c5d5db9bdf50@nazar.ca> (raw)

[-- Attachment #1: Type: text/plain, Size: 251 bytes --]

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.

Thanks,
Doug


[-- Attachment #2: log.txt --]
[-- Type: text/plain, Size: 1935 bytes --]

handle_gssd_upcall: 'mech=krb5 uid=0 service=* enctypes=18,17,16,23,3,1,2' (nfs/clnt4a0)
krb5_use_machine_creds: uid 0 tgtname (null)
gssd_refresh_krb5_machine_credential_internal: hostname=pixie.dragoninc.ca ple=(nil) service=(null) srchost=*
Full hostname for 'pixie.dragoninc.ca' is 'pixie.dragoninc.ca'
No key table entry found for *$@DRAGONINC.CA while getting keytab entry for '*$@DRAGONINC.CA'
No key table entry found for *$@DRAGONINC.CA while getting keytab entry for '*$@DRAGONINC.CA'
No key table entry found for root/*@DRAGONINC.CA while getting keytab entry for 'root/*@DRAGONINC.CA'
No key table entry found for nfs/*@DRAGONINC.CA while getting keytab entry for 'nfs/*@DRAGONINC.CA'
No key table entry found for host/*@DRAGONINC.CA while getting keytab entry for 'host/*@DRAGONINC.CA'
Scanning keytab for root/*@DRAGONINC.CA
Processing keytab entry for principal 'host/wraith.dragoninc.ca@DRAGONINC.CA'
We will NOT use this entry (host/wraith.dragoninc.ca@DRAGONINC.CA)
Processing keytab entry for principal 'host/wraith.dragoninc.ca@DRAGONINC.CA'
We will NOT use this entry (host/wraith.dragoninc.ca@DRAGONINC.CA)
Processing keytab entry for principal 'nfs/wraith.dragoninc.ca@DRAGONINC.CA'
We will NOT use this entry (nfs/wraith.dragoninc.ca@DRAGONINC.CA)
Processing keytab entry for principal 'nfs/wraith.dragoninc.ca@DRAGONINC.CA'
We will NOT use this entry (nfs/wraith.dragoninc.ca@DRAGONINC.CA)
Scanning keytab for nfs/*@DRAGONINC.CA
Processing keytab entry for principal 'host/wraith.dragoninc.ca@DRAGONINC.CA'
We will NOT use this entry (host/wraith.dragoninc.ca@DRAGONINC.CA)
Processing keytab entry for principal 'host/wraith.dragoninc.ca@DRAGONINC.CA'
We will NOT use this entry (host/wraith.dragoninc.ca@DRAGONINC.CA)
Processing keytab entry for principal 'nfs/wraith.dragoninc.ca@DRAGONINC.CA'
We WILL use this entry (nfs/wraith.dragoninc.ca@DRAGONINC.CA)
Success getting keytab entry for nfs/*@DRAGONINC.CA

             reply	other threads:[~2020-06-29 20:09 UTC|newest]

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

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=e61057cc-6c4b-6d88-aab2-c5d5db9bdf50@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).