Roberto C. Sánchez wrote:
> On Wed, Mar 07, 2018 at 11:08:05PM +0100, Sven Hartge wrote:
>> This is why you use libpam-ldapd (instead of libpam-ldap) in
>> combination with libnss-ldapd (instead of libnss-ldap).
>>
>> Its design with a separate daemon (nslcd) doing the actual LDAP
>> connection
On Wed, Mar 07, 2018 at 11:08:05PM +0100, Sven Hartge wrote:
>
> This is why you use libpam-ldapd (instead of libpam-ldap) in combination
> with libnss-ldapd (instead of libnss-ldap).
>
> Its design with a separate daemon (nslcd) doing the actual LDAP
> connection is far superior compared to the
David Parker wrote:
> Well, crap. It turns out this isn't a problem. PAM is configured for
> LDAP authentication and so it opens a connection each time I log in,
> owned by my sshd process, even though it's not using LDAP
> authentication for root. And the other LDAP queries I'm seeing are
> b
Well, crap. It turns out this isn't a problem. PAM is configured for LDAP
authentication and so it opens a connection each time I log in, owned by my
sshd process, even though it's not using LDAP authentication for root. And
the other LDAP queries I'm seeing are being sent when users authenticat
4 matches
Mail list logo
