have tested using libsasl2-modules=2.1.27~101-g0780600+dfsg-3ubuntu2.2,
libsasl2-modules-db=2.1.27~101-g0780600+dfsg-3ubuntu2.2, libsasl2
-modules-gssapi-mit=2.1.27~101-g0780600+dfsg-3ubuntu2.2 and
adcli=0.8.2-1ubuntu1.1
Join to AD without specifying --use-ldaps seemed to run without error.
So
Thanks for the suggestion, I've checked and on that specific machine
pam_localuser wasn't present. I'm not sure why though as the pam
config should have been generated by the default package hooks that
update the pam files as packages are installed.
Possibly the lack of the line is some intera
Public bug reported:
If you install sssd on a machine and then stop the service. Logins as
local users fail (until sssd is started back up).
e.g. When trying to login using the correct password for 'localadmin', the
login fails with the auth logs recording messages like;
pam_sss(login:auth): R
I hit this bug as well. In my testing though if --use-ldaps is
specified, the join no longer hangs.
So I'm wondering if possibly the GSS-SPENGO support is somehow relying
on something from --use-ldaps code or should be set to only be active
if --use-ldaps is set?
--
You received this bug
Public bug reported:
The nfs-ganesha package installs the systemd unit file
/lib/systemd/system/nfs-ganesha-config.service
which specifies
ExecStart=/usr/lib/ganesha/nfs-ganesha-config.sh
but no such file is provided by the package so the service fails to
start.
The package does install a /usr/
Public bug reported:
The 4.1-0ubuntu1.1 update to libmsn-dev in lucid alters /usr/include/msn/soap.h
to include the line
#include "xmlParser.h"
however no xmlParser.h file is provided in the dev package so when the
kdenetwork package is compiled it's compilation errors out with;
[ 37%] Buildi