Hi there,
sudo journalctl -u qubes-tunnel:
> systemd[1]: Starting qubes-tunnel.service - Tunnel service for Qubes
> proxyVM...
> su[640]: PAM unable to dlopen(/usr/lib64/security/pam_sss.so):
> /usr/lib64/security/pam_sss.so: cannot open shared object file: >
> su[640]: PAM adding faulty module: /usr/lib64/security/pam_sss.so
> su[640]: (to user) root on none
> su[640]: pam_unix(su-l:session): session opened for user
> user(uid=1000) by (uid=0)
> su[640]: pam_unix(su-l:session): session closed for user user
> systemd[1]: qubes-tunnel.service: Control process exited, code=exited,
> status=1/FAILURE
> qtunnel-setup[751]: STOP-ing network forwarding!
> systemd[1]: qubes-tunnel.service: Failed with result 'exit-code'.
> systemd[1]: Failed to start qubes-tunnel.service - Tunnel service for
> Qubes proxyVM.
/usr/lib64/security/pam_sss.so is part of
> sudo dnf install sssd-client
>
(directly, not part of the dependencies libsss_nss_idmap or libsss_idmap)
notably, fedora-34 template does not have sssd-client or its
dependencies libsss_nss_idmap or libsss_idmap installed and the .so file
does not exists there, but nevertheless "sudo journalctl -u
qubes-tunnel" does not show the error
notably even with this error my openvpn-configuration works fine!
Does somebody know:
1) What this dependency is used for
2) Why this dependency is not needed in fedora 34
3) Which circumstances cause the need for this dependency
4) how to properly report this?
https://github.com/QubesOS-contrib/qubes-tunnel has "issues" disabled ...
Thanks