All of lore.kernel.org
 help / color / mirror / Atom feed
From: marcel@linux-ng.de
To: linux-nfs@vger.kernel.org
Subject: nfs-utils: rpc.svcgssd bug reading /etc/nfs.conf
Date: Mon, 06 Jun 2022 18:14:05 +0000	[thread overview]
Message-ID: <bf4aa2c82bfef19304d7a458a2a8fb28@linux-ng.de> (raw)

Hi there,

please don't hesitate to direct me somewhere else in case this is not the right place to report
bugs concerning nfs-utils.

I found a bug in nfs-utils concerning the rpc.svcgssd daemon while I was trying to set the
principal name in /etc/nfs.conf:

[svcgssd]
principal=nfs/myhost.mydomain.de@MYDOMAIN.DE

However rpc.svcgssd refused to start - complaining about not being able to find the principal in
the keytab.
When specified on command line (using the -p option) things worked however.

So I took a look at the code and found the problem in nfs-utils-2.6.1/utils/gssd/svcgssd.c.
The problem seems to be here:

/* We don't need the config anymore */
conf_cleanup();

This is called right after parsing the config file(s), but before calling gssd_acquire_cred().
At the time it is called the variable "principal" does no longer contain the data read from the
config file.

Moving conf_cleanup() to the end of the code helps.

As I first encountered this on Ubuntu 22.04 I also opened a Launchpad bug report:
s. https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1977745

Maybe someone can fix this for the next release.

Best regards,
Marcel

             reply	other threads:[~2022-06-06 18:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-06 18:14 marcel [this message]
2022-06-06 18:29 ` nfs-utils: rpc.svcgssd bug reading /etc/nfs.conf Steve Dickson

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=bf4aa2c82bfef19304d7a458a2a8fb28@linux-ng.de \
    --to=marcel@linux-ng.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.