All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Ed Street <edstreet@street-tek.com>
Cc: "'SE-Linux'" <selinux@tycho.nsa.gov>
Subject: Re: adduser script
Date: Wed, 19 May 2004 13:32:43 +0000	[thread overview]
Message-ID: <20040519133243.GD4221@lkcl.net> (raw)
In-Reply-To: <20040519115634.9C18D3A4054@abyss.simplyaquatics.com>

On Wed, May 19, 2004 at 07:56:33AM -0400, Ed Street wrote:
> Hello,
> 
> That should not be to difficult, just pass a context(s) switch or prompt for
> it.

 investigating more, i find a package adduser-ng (adduser next
 generation).

 it has a plugin system which has the ability to pass options up to
 the main commandline usage, and even the /etc/shadow setup is
 done as a plugin.

 ... it's written in perl.

 assuming i can get over my gratuitous and unnecessary lack of respect
 for ptooey^H^H^H^H^Herl, could someone advise me if it's a simple
 enough and acceptable procedure to:

	 - accept an option --selinux-roles="staff sysadm user system"
	   (or maybe staff_r etc. because it will be less perl coding for
	    ME!)

	 - parse the /etc/selinux/users file looking for the string
	   "user [$username] roles"

	 - replace the relevant line with the roles _r
	   (if i can be bothered)

	 - do a syscall to "make -C /etc/selinux install"

 and leave it at that - all pretty much hard-coded.

 - no checking / parsing of the roles because other roles may be
   added by the sysadmin


 thoughts, comments?
 
 how do i do a delete?
 _do_ i have to do a delete?

 if a role is left in the /etc/selinux/users and there is no passwd
 entry, does it matter?

 l.

> -----Original Message-----
> From: owner-selinux@tycho.nsa.gov [mailto:owner-selinux@tycho.nsa.gov] On
> Behalf Of Luke Kenneth Casson Leighton
> Sent: Wednesday, May 19, 2004 5:17 AM
> To: SE-Linux
> Subject: adduser script
> 
> has anyone considered writing an adduser script modification
> for selinux that adds users to /etc/selinux/users?
> 
> ---
> 
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.687 / Virus Database: 448 - Release Date: 5/16/2004
>  
> 

-- 
-- 
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 13:36 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
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 [this message]
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=20040519133243.GD4221@lkcl.net \
    --to=lkcl@lkcl.net \
    --cc=edstreet@street-tek.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.