[Bug 1906627] Re: GSS-SPNEGO implementation in cyrus-sasl2 is incompatible with Active Directory, causing recent adcli regression

2020-12-10 Thread Jason Alavaliant
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 from my perspective I'd say those combination of packages fixes the
problem.

Thanks
-J

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906627

Title:
  GSS-SPNEGO implementation in cyrus-sasl2 is incompatible with Active
  Directory, causing recent adcli regression

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adcli/+bug/1906627/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1906739] Re: default sssd pam config breaks local user logins if sssd isn't running

2020-12-10 Thread Jason Alavaliant
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 interaction with how packages are
automatically installed our machines via puppet.But since it looks
like it's a local problem with our setup,  am happy for this to be
closed.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906739

Title:
  default sssd pam config breaks local user logins if sssd isn't running

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1906739/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1906739] [NEW] default sssd pam config breaks local user logins if sssd isn't running

2020-12-03 Thread Jason Alavaliant
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): Request to sssd failed. Connection refused
FAILED LOGIN (1) on '/dev/tty1' FOR 'localadmin', Authentication failure
pam_sss(login:account): Request to sssd failed. Connection refused
login[31397]: Authentication service cannot retrieve authentication info

>From what I've found in testing. The problem comes from 
>/etc/pam.d/common-account
which by default specifies;

account [default=bad success=ok user_unknown=ignore]pam_sss.so

If that is changed to

account [default=ignore success=ok user_unknown=ignore]pam_sss.so

The pam stack doesn't exit out straight away when sssd can't be
connected to,  and instead pam_unix.so is still used.

So far in my testing I've not found any problems from the change,
network logins with bad passwords are still rejected etc. As is
understand it the change is making pam skip over pam_sss.so if it
returns a result other than successful login.   So I'm not seeing how it
could cause problems.

Can the default pam configuration set by the sssd package please be
updated to change the default=bad to default=ignore   so that a broken
sssd daemon doesn't stop all local account logins from working as well?

Thanks
-J

** Affects: sssd (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906739

Title:
  default sssd pam config breaks local user logins if sssd isn't running

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1906739/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1906627] Re: adcli fails, can't contact LDAP server

2020-12-03 Thread Jason Alavaliant
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 notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906627

Title:
  adcli fails, can't contact LDAP server

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adcli/+bug/1906627/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1832159] [NEW] nfs-ganesha-config.service fails to start due to bad path

2019-06-09 Thread Jason Alavaliant
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/lib/nfs-ganesha-config.sh so I'd presume
either the file is being installed to the wrong location when the
package is being built or the nfs-ganesha-config.service needs it's
ExecStart= value corrected.

I'm using bionic/18.04,   I've not tested for if the bug is present in
other package versions.

** Affects: nfs-ganesha (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1832159

Title:
  nfs-ganesha-config.service fails to start due to bad path

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nfs-ganesha/+bug/1832159/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 901389] [NEW] 4.1-0ubuntu1.1 breaks compilation of kdenetwork package on lucid

2011-12-07 Thread Jason Alavaliant
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%] Building CXX object 
kopete/protocols/wlm/CMakeFiles/kopete_wlm.dir/ui/wlmeditaccountwidget.o
cd kopete/protocols/wlm  /usr/bin/g++   -DMAKE_KOPETE_WLM_LIB -D_BSD_SOURCE 
-D_XOPEN_SOURCE=500 -D_BSD_SOURCE -DQT_NO_STL -DQT_NO_CAST_TO_ASCII 
-D_REENTRANT -DKDE_DEPRECATED_WARNINGS -DHAVE_GIFLIB -g -O2 -g -Wall -O2 
-Wnon-virtual-dtor -Wno-long-long -ansi -Wundef -Wcast-align -Wchar-subscripts 
-Wall -W -Wpointer-arith -Wformat-security -fno-exceptions -DQT_NO_EXCEPTIONS 
-fno-check-new -fno-common -Woverloaded-virtual -fno-threadsafe-statics 
-fvisibility=hidden -fvisibility-inlines-hidden -DNDEBUG -DQT_NO_DEBUG -fPIC 
-I. -I../../../../kopete/protocols/wlm -I../../../.. -I../../.. -I../.. 
-I../../../../kopete/libkopete -I../../libkopete 
-I../../../../kopete/libkopete/ui -I../../libkopete/ui 
-I../../../../kopete/libkopete/private 
-I../../../../kopete/libkopete/contactlist -I../../../../kopete/libkopete/tasks 
-I../../../../kopete/protocols/wlm/ui -I/usr/include/KDE -I/usr/include/qt4/KDE 
-I/usr/include/qt4 -I/usr/include/qt4/phonon -I/usr/include/qt4/QtXmlPatterns 
-I/usr/include/qt4/QtXml -I/usr/include/qt4/QtWebKit 
-I/usr/include/qt4/QtUiTools -I/usr/include/qt4/QtTest -I/usr/include/qt4/QtSvg 
-I/usr/include/qt4/QtSql -I/usr/include/qt4/QtScriptTools 
-I/usr/include/qt4/QtScript -I/usr/include/qt4/QtOpenGL 
-I/usr/include/qt4/QtNetwork -I/usr/include/qt4/QtMultimedia 
-I/usr/include/qt4/QtHelp -I/usr/include/qt4/QtDesigner 
-I/usr/include/qt4/QtDBus -I/usr/include/qt4/QtAssistant 
-I/usr/include/qt4/Qt3Support -I/usr/include/qt4/QtGui 
-I/usr/include/qt4/QtCore -I/usr/include/qt4/Qt 
-I/usr/share/qt4/mkspecs/default   -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -o 
CMakeFiles/kopete_wlm.dir/ui/wlmeditaccountwidget.o -c 
../../../../kopete/protocols/wlm/ui/wlmeditaccountwidget.cpp
In file included from /usr/include/msn/notificationserver.h:36,
 from /usr/include/msn/msn.h:33,
 from ../../../../kopete/protocols/wlm/wlmsocket.h:22,
 from ../../../../kopete/protocols/wlm/wlmlibmsn.h:21,
 from ../../../../kopete/protocols/wlm/wlmserver.h:20,
 from ../../../../kopete/protocols/wlm/wlmaccount.h:24,
 from 
../../../../kopete/protocols/wlm/ui/wlmeditaccountwidget.cpp:33:
/usr/include/msn/soap.h:38:23: error: xmlParser.h: No such file or directory
In file included from /usr/include/msn/notificationserver.h:36,
 from /usr/include/msn/msn.h:33,
 from ../../../../kopete/protocols/wlm/wlmsocket.h:22,
 from ../../../../kopete/protocols/wlm/wlmlibmsn.h:21,
 from ../../../../kopete/protocols/wlm/wlmserver.h:20,
 from ../../../../kopete/protocols/wlm/wlmaccount.h:24,
 from 
../../../../kopete/protocols/wlm/ui/wlmeditaccountwidget.cpp:33:
/usr/include/msn/soap.h:211: error: expected ‘;’ before ‘(’ token
../../../../kopete/protocols/wlm/ui/wlmeditaccountwidget.cpp: In constructor 
‘WlmEditAccountWidget::WlmEditAccountWidget(QWidget*, Kopete::Account*)’:
../../../../kopete/protocols/wlm/ui/wlmeditaccountwidget.cpp:45: warning: 
unused variable ‘config’
make[3]: *** 
[kopete/protocols/wlm/CMakeFiles/kopete_wlm.dir/ui/wlmeditaccountwidget.o] 
Error 1
make[3]: Leaving directory 
`/tech/home/jasong/src/kde/krfb-shift-key-patching/kdenetwork-4.4.5/obj-x86_64-linux-gnu'
make[2]: *** [kopete/protocols/wlm/CMakeFiles/kopete_wlm.dir/all] Error 2
make[2]: Leaving directory 
`/tech/home/jasong/src/kde/krfb-shift-key-patching/kdenetwork-4.4.5/obj-x86_64-linux-gnu'
make[1]: *** [all] Error 2
make[1]: Leaving directory 
`/tech/home/jasong/src/kde/krfb-shift-key-patching/kdenetwork-4.4.5/obj-x86_64-linux-gnu'
make: *** [debian/stamp-makefile-build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2


This can be worked around by downgrading the libmsn packages back to 
4.1-0ubuntu1 but it's hardly an ideal state for things to be in.(and a 
waste of time for developers who have to track down why packages don't build 
anymore,  I suspect the maintainer already knows about this bug but putting 
something in the bug tracker anyway so other people in my situation will be 
able to find the problem faster and hopefully not spend as much time as I did 
wondering why building kdenetwork was broken).

** Affects: libmsn (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/901389

Title:
  4.1-0ubuntu1.1 breaks compilation of kdenetwork package on lucid

To manage notifications about this bug go to: