linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.com>
To: Daniel Pocock <daniel@pocock.pro>,
	Niels Thykier <niels@thykier.net>,
	linux-nfs@vger.kernel.org, 852395@bugs.debian.org,
	Robbie Harwood <rharwood@club.cc.cmu.edu>
Cc: Debian kernel team <debian-kernel@lists.debian.org>
Subject: Re: Bug#852395: unblock: gssproxy/0.5.1-2
Date: Mon, 20 Mar 2017 16:07:40 +1100	[thread overview]
Message-ID: <87o9wwcz8j.fsf@notabene.neil.brown.name> (raw)
In-Reply-To: <f4e3252f-0115-954d-5749-c330c6905b75@pocock.pro>

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

On Sun, Mar 05 2017, Daniel Pocock wrote:

> On 05/03/17 19:42, Niels Thykier wrote:
>> On Sat, 04 Feb 2017 09:58:00 +0000 Niels Thykier <niels@thykier.net> wrote:
>>> Daniel Pocock:
>>>> [...]
>>>>
>>>> Upstream is not really supporting rpc.svcgssd any more, they actually
>>>> disabled it in the build so people can still have it as a transitional
>>>> measure in stretch.
>>>>
>>>> People shouldn't be using it in any new installations.  Offering them
>>>> gssproxy is a very sensible thing to do.
>>>>
>>>> Regards,
>>>>
>>>> Daniel
>>>>
>>> Debian kernel team <debian-kernel@lists.debian.org>
>>> Ok, follow up questions:
>>>
>>>  * Do you have an upstream reference to the state of rpc.svcgssd?
>
>
> http://git.linux-nfs.org/?p=steved/nfs-utils.git;a=commit;h=24b5d60d7f0a514310df810e3eb27b72f665febf
>
> "svcgssd: Disable support for the rpcsec_gss server by default
>
> At this point the gssproxy is better option than the
> svcgssd so the support is off by default.
>
> Use --enable-svcgss to re-enable the support"
>
> but it looks like it may not be completely abandoned, there have been
> other commits that mention gssd recently.
>
>
>>>
>>>  * Can we provide both rpc.svcgssd and gssproxy in Debian (with the
>>>    admin choosing) or is it an "xor"?
>>>
>
> I think there are two questions:
>
> a) can they both exist in different packages that conflict with each
> other?  I'm guessing that will probably be yes.
>
> b) can they both be installed simultaneously?  Possibly not (can anybody
> on the linux-nfs list answer?)

Yes, they can.
The systemd unit files are designed so that svcgssd will only be started
if gssproxy didn't start - and gssproxy is tried first.

If you use something other than systemd, similar logic would be needed.

NeilBrown


>
>
>>>  * If this package is unblocked, are there any changes needed in
>>>    nfs-common needed to support gssproxy?  (source upload, binNMU or
>>>    "just works with no further changes")
>>>
>
> I don't have time to investigate that right now, if anybody else has
> time to look more closely that would be great.
>
> Regards,
>
> Daniel
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  reply	other threads:[~2017-03-20  5:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <148524180980.26332.422684345851896222.reportbug@kirtar>
     [not found] ` <8ed20c71-d7e2-72e1-a8ce-c913f8e0fffd@thykier.net>
     [not found]   ` <17e5fbd0-9bb1-d7fa-6056-8adbda8a1f4d@pocock.pro>
     [not found]     ` <e157cdda-35b6-8643-7d9f-da79faec56f7@thykier.net>
     [not found]       ` <5df78805-b791-0a5e-3dcb-99792d78c3bd@thykier.net>
2017-03-05 19:09         ` Bug#852395: unblock: gssproxy/0.5.1-2 Daniel Pocock
2017-03-20  5:07           ` NeilBrown [this message]
2017-04-05 10:37             ` Niels Thykier

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=87o9wwcz8j.fsf@notabene.neil.brown.name \
    --to=neilb@suse.com \
    --cc=852395@bugs.debian.org \
    --cc=daniel@pocock.pro \
    --cc=debian-kernel@lists.debian.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=niels@thykier.net \
    --cc=rharwood@club.cc.cmu.edu \
    /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).