0.8.4: When stopping: free(): invalid pointer

[gssapi]

0.8.4: When stopping: free(): invalid pointer

[simo5]

Are you suing krb5 authentication for your NFS mounts? That's what gssproxy is used for normally.
You may see nfs related configuration files under /etc/gssproxy/99-nfs-client.conf
It is fine that the main gssproxy conf file is empty if thre are nor general directives to apply to change the default general configuration.

On libverto it is very odd if it is provided by the krb5 package. Krb5 does have an old vendored version of libeverto in case one is not installed on the system, but the correct way to build it would be to provide the verto package on the distro and then build krb5 against it.

For example in Fedora 34 we have libverto-0.3.2-1.fc34.x86_64.rpm which provides /usr/lib64/libverto.so.1.0.0

At any rate verto_cleanup() is a function w/o parameters, if it crashes it means there is a bug in the verto version used in your distribution, or, potentially worse, there are two versions of libverto loaded in your address space (one linked by gssproxy, and one built statically into krb5) and symbols are clashing.

Nothing that can be solved on the gssproxy side at any rate.