All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simo Sorce <simo@redhat.com>
To: "Myklebust, Trond" <Trond.Myklebust@netapp.com>
Cc: "libtirpc-devel@lists.sourceforge.net"
	<libtirpc-devel@lists.sourceforge.net>,
	linux-nfs <linux-nfs@vger.kernel.org>,
	Steve Dickson <steved@redhat.com>
Subject: Re: Allow building libtirpc directly against GSSAPI
Date: Tue, 26 Mar 2013 11:49:52 -0400	[thread overview]
Message-ID: <1364312992.2660.126.camel@willson.li.ssimo.org> (raw)
In-Reply-To: <1364312636.4534.8.camel@leira.trondhjem.org>

On Tue, 2013-03-26 at 15:43 +0000, Myklebust, Trond wrote:
> On Tue, 2013-03-26 at 11:37 -0400, Simo Sorce wrote:
> > On Tue, 2013-03-26 at 15:25 +0000, Myklebust, Trond wrote:
> > > On Tue, 2013-03-26 at 10:41 -0400, Simo Sorce wrote:
> > > > Libgssglue is not really useful anymore, it is a sort of middleman that
> > > > wraps the actual GSSAPI that is already pluggable/extensible via shared
> > > > modules.
> > > > 
> > > > In particular libgssglue interferes with the workings of gss-proxy in my
> > > > case.
> > > > 
> > > > The attached patch makes building against libgssglue optional and
> > > > defaults to not build against libgssglue and instead builds directly
> > > > against the native GSSAPI.
> > > > 
> > > > ./configure --enable-gss
> > > > will now build against GSSAPI
> > > > 
> > > > ./configure --enable-gss --with-gssglue
> > > > will keep building against libgssglue in case someone still needs it for
> > > > whatever reason.
> > > > 
> > > > Simo.
> > > > 
> > > 
> > > Won't that be a backward compatibility issue?
> > 
> > What are you worried about exactly ? Is there a use case we should know
> > about ?
> 
> Building nfs-utils against existing older setups. There are a lot of
> users out there of 4-5 year old distros (including ones maintained by
> your employer).
> 
> Why isn't it safe to assume that if someone has libgssglue installed,
> then we should be building nfs-utils against it?

A foillowing patch for nfs-utils is coming, both the libtirpc and
nfs-utils patches will make building against libgssglue optional.

I see no value for selecting libgssglue by default though.
libgssglue does nothing but load the underlying gssapi library by
default anyway and adds nothing to that.

I am leaving the option to compile against libgssglue exactly for the
odd case where someone has a good reason to use it (very, very old
systems). In that case all they need to do is to run configure with
--enable-gss --with-gssglue

Simo.

-- 
Simo Sorce * Red Hat, Inc * New York


  reply	other threads:[~2013-03-26 15:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-26 14:41 Allow building libtirpc directly against GSSAPI Simo Sorce
2013-03-26 15:22 ` Steve Dickson
2013-03-26 15:25 ` Myklebust, Trond
2013-03-26 15:37   ` Simo Sorce
2013-03-26 15:43     ` Myklebust, Trond
2013-03-26 15:49       ` Simo Sorce [this message]
2013-03-26 15:56         ` Jim Rees
2013-03-26 16:56           ` Simo Sorce
2013-03-27  1:14 ` Alex Dubov
2013-04-02 18:02   ` 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=1364312992.2660.126.camel@willson.li.ssimo.org \
    --to=simo@redhat.com \
    --cc=Trond.Myklebust@netapp.com \
    --cc=libtirpc-devel@lists.sourceforge.net \
    --cc=linux-nfs@vger.kernel.org \
    --cc=steved@redhat.com \
    /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.