On Tue, Aug 20, 2019 at 02:01:40PM +0200, cedric hottier wrote:
> Dear SSSD users,
>
> I would like to share with you few issues I faced during the move from
> 1.16.3 to 2.2.0 sssd release.
> I am a Debian user and I did this move because Debian pushed the 2.2.0
> release in the testing branch.
>
> My configuration may seem exotic as I use 'files' as id_provider and
'krb5'
> as auth_provider.
>
> Initially with the 1.16 version I faced the following issue :
>
https://pagure.io/SSSD/sssd/issue/3591
>
> Thanks to Jakub Hrozek
>
<
https://lists.fedorahosted.org/archives/users/598050231053154702993168591...;,
> I was able to make it working with the following workaround :
> id_provider=proxy proxy_lib_name=files
> For those interested, the discussion thread is here :
>
https://lists.fedorahosted.org/archives/list/sssd-users@lists.fedorahoste...
>
>
> With the move to 2.2.0, I faced several issues...
> First, I had to remove the line services = nss, pam, ifp from sssd.conf
> because I use systemd.
> I think i fell in the bug described here :
>
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886483 . I do not know if
> it is a debian specific integration issue, or a sssd issue. I did not find
> any reference to sssd upstream bug, but in the meantime, it is written that
> "We believe that the bug you reported is fixed in the latest version of
sssd"
> . Not clear for me if they are talking about sssd debian package version,
> or upstream version.
> Anyway, I faced this issue with new debian package 2.2.0, let me know if it
> is a debian specific stuff to open a bug report on debian side.
>
> Once the previous issue was fixed, I faced a segmentation fault in
> libsss_proxy.so.
Hi,
I guess you are seeing
https://pagure.io/SSSD/sssd/issue/3931 which