Just tested the proposed gssproxy fix, and can confirm that it solved the issue
Tested on Ubuntu Focal (20.04)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libselinux in Ubuntu.
https://bugs.launchpad.net/bugs/1788459
I can confirm that manual build and install of gssproxy 0.8.4 works on my
ubuntu 20.04 server.
(that version has the patch mentioned above)
gssproxy solves my original issue of rpc-svcgssd hanging on large
kerberos tickets https://bugs.launchpad.net/ubuntu/+source/nfs-
utils/+bug/1466654
gssproxy/focal,now 0.8.2-2 amd64 [installed]
libselinux1/focal,now 3.0-1build2 amd64 [installed,automatic]
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to krb5 in Ubuntu.
https://bugs.launchpad.net/bugs/1788459
Title:
I couldn't get it to generate a coredump. But I ran it with valgrind
Hope this helps
valgrind -v /usr/sbin/gssproxy --interactive --debug --debug-level=3
--socket=/run/gssproxy.sock
==29249== Memcheck, a memory error detector
==29249== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et
** Attachment added: "/var/crash/_usr_sbin_gssproxy.0.crash"
https://bugs.launchpad.net/ubuntu/+source/gssproxy/+bug/1788459/+attachment/5507903/+files/_usr_sbin_gssproxy.0.crash
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
The reason we want gssproxy, and not the default rpc-gssd and rpc-
svcgssd services is that we are using active directory, and most of our
accounts are members of many groups, causing gssd to fail. This is a
known issue and is one of the things that gssproxy solves.
>>The reason we did this was
Trying to get gssproxy working with NFS (rpc-gssd and rpc-svcgssd) on Ubuntu
20.04
Following https://github.com/gssapi/gssproxy/blob/main/docs/NFS.md
/etc/gssproxy/gssproxy.conf
[gssproxy]
debug = true
debug_level = 3
/etc/gssproxy/25-nfs-server.conf
[service/nfs-server]
7 matches
Mail list logo
