From: Steve Dickson <SteveD@redhat.com>
To: Kevin Coffman <kwc@citi.umich.edu>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH] Add requirement for newer libgssglue for svcgssd -n option
Date: Thu, 30 Jun 2011 11:24:23 -0400 [thread overview]
Message-ID: <4E0C9527.9060503@RedHat.com> (raw)
In-Reply-To: <20110629183721.23198.57774.stgit@jazz.citi.umich.edu>
On 06/29/2011 02:37 PM, Kevin Coffman wrote:
> SNAFU. This came to my attention minutes after 1.2.4 was
> released...
>
> Changes in commit d6c1b35c require that gss_acquire_cred()
> is now called when the "-n" option is used. This requires an
> updated libgssglue which properly handles name GSS_C_NO_NAME
> as input to gss_import_name()/gss_acquire_cred().
>
> Add a requirement for the newer version.
>
> Without the newer libgssglue, when svcgssd is started with "-n"
> you will see the error message, "ERROR: GSS-API: error in
> gss_acquire_cred(): GSS_S_BAD_NAME (An invalid name was supplied)
> - Unknown error"
> ---
Committed.. Unfortunately post 1.2.4 release...
steved.
>
> aclocal/rpcsec_vers.m4 | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/aclocal/rpcsec_vers.m4 b/aclocal/rpcsec_vers.m4
> index 25902ca..8218372 100644
> --- a/aclocal/rpcsec_vers.m4
> +++ b/aclocal/rpcsec_vers.m4
> @@ -1,7 +1,7 @@
> dnl Checks librpcsec version
> AC_DEFUN([AC_RPCSEC_VERSION], [
>
> - PKG_CHECK_MODULES([GSSGLUE], [libgssglue >= 0.1])
> + PKG_CHECK_MODULES([GSSGLUE], [libgssglue >= 0.3])
>
> dnl TI-RPC replaces librpcsecgss
> if test "$enable_tirpc" = no; then
>
prev parent reply other threads:[~2011-06-30 15:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-29 18:37 [PATCH] Add requirement for newer libgssglue for svcgssd -n option Kevin Coffman
2011-06-30 0:38 ` Kevin Coffman
2011-06-30 15:24 ` Steve Dickson [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=4E0C9527.9060503@RedHat.com \
--to=steved@redhat.com \
--cc=kwc@citi.umich.edu \
--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.