[SSSD] SIGSEGV in sssd_be using ldap_init_fd

Jan Zelený jzeleny at redhat.com
Fri Jul 29 12:09:00 UTC 2011


> Jan Zelený wrote:
> > Yes, in recent versions you should have something like
> > 
> > libnss3.so()(64bit)
> 
> Just to confirm, this all now works perfectly and either GSSAPI or TLS.
> Am I right in assuming they are mutually exclusive?

Yes, they should be. However I'm not entirely sure if they are made mutually 
exclusive in the code. We shall verify this.

> I'm switching to sssd to bind to an AD domain with >100k user objects
> and nearly 200k groups.  sssd seems to be making a really good stab at
> coping with that, in a way that an unmodified nss_ldap/nscd simply
> couldn't.  To be honest, that's pretty remarkable.

Thanks, we're always happy to hear that.

> Many thanks for your help with this, it really is appreciated.
> 
> jh

Jan
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <https://lists.fedorahosted.org/pipermail/sssd-devel/attachments/20110729/0f1a34f2/attachment.sig>


More information about the sssd-devel mailing list