severity 368297 important thanks I spend some time tracking down this issue and here's what I found:
- The only ssl option that has an effect is "start_tls", which should enable tls no matter ldap:// or ldaps:// is used. - According to some stuff I read on the web the sudo guys prefer tls over ldap:// and even called ldaps usage deprecated. - Authorization is always done via your normal pam setting. The sudo-ldap connection is only to retrieve the info about what a user may do. I certainly was able to reproduce this bug, so I see no way to close it. To find a fix we probably need someone with libldap knowledge to look at the sources. But I see several ways to use the package. Or in other words the package is not unusable. This is why I downgraded it. Michael -- Michael Meskes Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED] Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
