Good news Rob,
apparently it ended up being a SELinux policy issue,
On Tue, 2017-03-28 at 17:44 +0200, Rob Verduijn wrote:
I guess this has low priority for the nfs devs.
Any workaround for this that does not require creating a service account in
2017-03-10 12:37 GMT+01:00 Rob Verduijn <rob.verduijn(a)gmail.com>:
> Cool...this thing was driving me nuts
> Looking forward to the patch.
> 2017-03-10 2:14 GMT+01:00 Robbie Harwood <rharwood(a)redhat.com>:
>> Rob Verduijn <rob.verduijn(a)gmail.com> writes:
>> > I've tried quite a lot of things (including the very latest version
>> > of gssproxy) but I keep failing to get it to work on fedora25.
>> > So in a last ditch attempt I created a reproducer in the form of a
>> > script that creates a test environment that has the problem.
>> Hi Rob,
>> Thanks for the (maximally) detailed reproducer. I was able to observe
>> the issue on my end. I observed that GSS_USE_PROXY=yes is indeed set in
>> rpc.gssd's environment. gssproxy isn't logging anything because it
>> never gets invoked. rpc.gssd has broken the environment variable which
>> we check using secure_getenv().
>> I've opened https://bugzilla.redhat.com/show_bug.cgi?id=1430963
gss-proxy mailing list -- gss-proxy(a)lists.fedorahosted.org
To unsubscribe send an email to gss-proxy-leave(a)lists.fedorahosted.org
Simo Sorce * Red Hat, Inc * New York