All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Frank Mayer <mayerf@tresys.com>, dac@tresys.com
Cc: "'SE-Linux'" <selinux@tycho.nsa.gov>
Subject: Re: adduser script
Date: Wed, 19 May 2004 14:19:02 +0000	[thread overview]
Message-ID: <20040519141902.GG4221@lkcl.net> (raw)
In-Reply-To: <00bf01c43d98$482f4fc0$4c0c010a@columbia.tresys.com>

On Wed, May 19, 2004 at 07:56:11AM -0400, Frank Mayer wrote:
> See seuser and the seuser* scripts in the setools package
 
 ah _ha_.

 okay.

 these are a very good base for adoption / adaption into adduser.

 unfortunately, the programs call useradd directly, which is what
 adduser-ng does [in a plugin].

 frank, would you be willing to split out the functionality
 of seuseradd etc. that deals with /etc/selinux/users into
 _separate_ programs?

 and make seuseradd etc. call those programs?

 at the moment, the structure is like this:

 seuseradd ---> useradd [-> accesses /etc/passwd]
            |
			|-> direct access to /etc/selinux/users

 and adduser-ng does this, with plugins being optional:

 adduser-ng ---> useradd [-> accesses /etc/passwd]
             |
			 |-> exim4plugin [-> accesses /etc/aliases]
			 |
			 |-> eximplugin [-> accesses /etc/aliases]
			 |
			 |-> PasswdUser plugin [-> direct access to /etc/shadow]
   
  
  what i would like to see is this:

 seuseradd ---> useradd [-> accesses /etc/passwd]
            |
			|-> addseuser [-> direct access to /etc/selinux/users]


 then i could _very_ easily do this, with oh about 1/2 a days' work:

 adduser-ng ---> useradd [-> accesses /etc/passwd]
             |
			 |-> exim4plugin [-> accesses /etc/aliases]
			 |
			 |-> eximplugin [-> accesses /etc/aliases]
			 |
			 |-> PasswdUser plugin [-> direct access to /etc/shadow]
             |
			 |-> addseuser [-> direct access to /etc/selinux/users]


 where addseuser is the functionality of the present seuseradd
 that manages /etc/selinux/users, split out into a separate program.

 etc.  same for seuserdel etc.


 go on, go on, you know you want to :)

 pleeease?

 everyone gains, because then the [standard] program adduser could be
 used to manage selinux users.

 sincerely,

 l.


> owner-selinux@tycho.nsa.gov wrote:
> > Subject: adduser script
> > 
> > 
> > has anyone considered writing an adduser script modification
> > for selinux that adds users to /etc/selinux/users?
> 
> 
> --
> 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.

-- 
-- 
expecting email to be received and understood is a bit like
picking up the telephone and immediately dialing without
checking for a dial-tone; speaking immediately without listening
for either an answer or ring-tone; hanging up immediately and
believing that you have actually started a conversation.
--
<a href="http://lkcl.net">      lkcl.net      </a> <br />
<a href="mailto:lkcl@lkcl.net"> lkcl@lkcl.net </a> <br />


--
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:[~2004-05-19 14:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-19  9:17 adduser script Luke Kenneth Casson Leighton
2004-05-19 11:56 ` Frank Mayer
2004-05-19 14:19   ` Luke Kenneth Casson Leighton [this message]
2004-05-19 14:53   ` Luke Kenneth Casson Leighton
2004-05-19 16:10     ` Frank Mayer
2004-05-19 17:18       ` Luke Kenneth Casson Leighton
2004-05-19 11:56 ` Ed Street
2004-05-19 13:32   ` Luke Kenneth Casson Leighton
2004-05-19 13:44     ` Ed Street
2004-05-19 14:21       ` Luke Kenneth Casson Leighton
2004-05-19 15:15     ` Luke Kenneth Casson Leighton

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=20040519141902.GG4221@lkcl.net \
    --to=lkcl@lkcl.net \
    --cc=dac@tresys.com \
    --cc=mayerf@tresys.com \
    --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.