All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel J Walsh <dwalsh@redhat.com>
To: Ivan Gyurdiev <ivg2@cornell.edu>, SE Linux <selinux@tycho.nsa.gov>
Subject: Why are we managing seusers file via libsemanage?
Date: Mon, 16 Jan 2006 22:49:39 -0500	[thread overview]
Message-ID: <43CC6953.4060901@redhat.com> (raw)

I don't recall why we did this?

I am now thinking this is not a good idea.  People were told to edit the 
/etc/selinux/POLICYTYPE/seusers file to change the default level at 
login, now we do this via libsemanage.  But doing this via libsemanage 
eliminates us from being able to distribute this information via say LDAP.

I think that seusers and setrans.conf should be left as flat files and 
allowed to be distributed via ldap.  We can allow the semanage tool and 
others to modify them and verify the data entry, but not manage them via 
the library.

Dan


--
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-17  3:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-17  3:49 Daniel J Walsh [this message]
2006-01-17  5:27 ` Why are we managing seusers file via libsemanage? Joshua Brindle
2006-01-17  5:33   ` Joshua Brindle
2006-01-17  7:36     ` Ivan Gyurdiev
2006-01-17  8:10       ` Ivan Gyurdiev
2006-01-17  7:16   ` Ivan Gyurdiev
2006-01-17  7:57 ` Ivan Gyurdiev
2006-01-17 18:02   ` Daniel J Walsh
2006-01-17 18:39     ` Ivan Gyurdiev
  -- strict thread matches above, loose matches on Subject: below --
2006-01-17 16:56 schaufler-ca.com - Casey Schaufler
2006-01-17 19:02 ` 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=43CC6953.4060901@redhat.com \
    --to=dwalsh@redhat.com \
    --cc=ivg2@cornell.edu \
    --cc=selinux@tycho.nsa.gov \
    /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.