From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <43CE8AD6.7050109@redhat.com> Date: Wed, 18 Jan 2006 13:37:10 -0500 From: Daniel J Walsh MIME-Version: 1.0 To: Ivan Gyurdiev CC: SELinux List , Joshua Brindle Subject: Re: Seusers vs ldap References: <43CE880B.3020908@cornell.edu> In-Reply-To: <43CE880B.3020908@cornell.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Sender: owner-selinux@tycho.nsa.gov List-Id: selinux@tycho.nsa.gov Ivan Gyurdiev wrote: > How would we go about implementing LDAP support for seusers in > libsemanage? > I asked Joshua about this on IRC, but I think we to plan this on list. > > I think the most important question to be decided is whether we'll use > libldap directly, or execute external programs to work with LDAP? The > first option makes libsemanage always linked to libldap. Why not loadable module? > > I also don't quite understand the role of the system-wide default > properties in ldap.conf. Joshua is telling me we'll need a server, > context, and keys specific to semanage (so we have to write all > ldap-related things in semanage.conf), but I'm not sure why the > context and server can't be shared with ldap.conf if necessary - I'm > probably still not understanding how this works - I have very limited > knowledge of ldap at this point. If you open up system-config-auth on > fedora, they seem to share the LDAP config for authentication and user > info, if you enable both of them. > > Also, do we have to write a schema? Does that schema get added to the > slapd package? We want support for Fedora-Directory also. -- This message was distributed to subscribers of the selinux mailing list. If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with the words "unsubscribe selinux" without quotes as the message.