pam_ldap - trouble understanding the do_authentication function
- To: pam-list@xxxxxxxxxx
- Subject: pam_ldap - trouble understanding the do_authentication function
- From: vidya chandrasekaran <sc_vidya@xxxxxxxxx>
- Date: Sat, 10 Dec 2005 05:12:16 -0800 (PST)
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=Qi0vrPMU6D/juxVnCLEw/XVGe1LEHgGDUouFy99GZOPT8wOlwVsE1pKhxKVzpnoGWVVwazU/YK3MSOyZKDFyoWxB/+wzbu1V+X2+Ww6zWz6AC6kXP7JMKKebn1GzOOl6h0JPZAYOSn1vKb9Dz80D4RG2jSPb3NVMuk+vXFm3uyE= ;
- Reply-to: Pluggable Authentication Modules <pam-list@xxxxxxxxxx>
- Sender: pam-list-bounces@xxxxxxxxxx
Hi,
I have been reading the source of pam_ldap(pam_ldap-180)
From what i understand of the authentication logic,
1. The username being authenticated is searched in the ldap directory to get the userdn (_get_user_info ()), following which
2. a simple bind is attempted. (_connect_as_user)
What escapes me is this, why a _connect_anonymously() call follwing step 2
Any pointer will be much appreciated.
Thanks
Vidya
Yahoo! Shopping
Find Great Deals on Holiday Gifts at Yahoo! Shopping _______________________________________________
Pam-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/pam-list
[Home]
[Kernel List]
[Red Hat Install]
[Linux for the blind]
[Red Hat Watch List]
[Gimp]
[Kerberos: The Definitive Guide]
| &nsp; |
 |