All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ivan Gyurdiev <ivg2@cornell.edu>
To: SELinux List <SELinux@tycho.nsa.gov>
Cc: Joshua Brindle <jbrindle@tresys.com>, Daniel J Walsh <dwalsh@redhat.com>
Subject: Seusers vs ldap
Date: Wed, 18 Jan 2006 11:25:15 -0700	[thread overview]
Message-ID: <43CE880B.3020908@cornell.edu> (raw)

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.

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?

--
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.

             reply	other threads:[~2006-01-18 18:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-18 18:25 Ivan Gyurdiev [this message]
2006-01-18 18:37 ` Seusers vs ldap Daniel J Walsh
2006-01-18 21:13   ` Joshua Brindle
2006-01-20  8:52     ` Ivan Gyurdiev
2006-01-20 13:10       ` Joshua Brindle
2006-01-20 13:25         ` Ivan Gyurdiev
2006-01-20 12:00 ` LDAP vs Dbase semantics Ivan Gyurdiev
2006-01-20 12:13   ` Ivan Gyurdiev

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=43CE880B.3020908@cornell.edu \
    --to=ivg2@cornell.edu \
    --cc=SELinux@tycho.nsa.gov \
    --cc=dwalsh@redhat.com \
    --cc=jbrindle@tresys.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.