From: Daniel J Walsh <dwalsh@redhat.com>
To: Ivan Gyurdiev <ivg2@cornell.edu>
Cc: russell@coker.com.au, SELinux List <SELinux@tycho.nsa.gov>,
Stephen Smalley <sds@tycho.nsa.gov>
Subject: Re: [SEMANAGE] Further bugfixes
Date: Fri, 20 Jan 2006 09:03:13 -0500 [thread overview]
Message-ID: <43D0EDA1.5070002@redhat.com> (raw)
In-Reply-To: <43D0D8E2.2020304@cornell.edu>
Ivan Gyurdiev wrote:
>
>> I think that all of these should be changed similar to my revised man
>> page (which I posted under the subject "semanage patch" on the 14th
>> of Jan).
>>
>> semanage fcontext -{a|d|m} [-hfrst] CONTEXT_EXPRESSION\n\
>> semanage interface -{a|d|m} [-tr] INTERFACE_NAME\n\
>> semanage login -{a|d|m} [-sr] LOGIN_NAME\n\
>> semanage port -{a|d|m} [-tpr] PORT | PORT_RANGE\n\
>>
I like this format
>> The convention is that anything within [] is optional, however it is
>> not optional to have one of 'a', 'd', or 'm', it is required to have
>> exactly one of them.
>>
> Technically -p is required for ports, since it is part of the port key.
> Also, there's required parameters on add that you must enter (but I
> guess this is better left out of the manpage).
>> Also there should be a line such as the following to indicate the
>> ways in which the "-l" option can be used (it can't be used in
>> conjunction with any other option):
>> semanage {login|user|port} -l
>>
>> Do "interface" and "fcontext" support the "-l" option?
>>
> Sure.. try it..
>> I would offer a patch for this, but I think we have enough unmerged
>> patches for the semanage utility floating around at the moment. Once
>> we get the current patches sorted out I'll be happy to write a patch
>> for this.
>>
> I think most of them have been merged, but I'm not sure which ones
> you're referring to.
>> Finally, when semanage development slows down a bit we will have to
>> put in some decent error checking for command-line parameters.
>> Currently you can pass in parameters that are not used to a command
>> without an error or warning message. For example the following
>> command will work even though -R is not a valid option to the login
>> management interface.
>>
>> semanage login -a -s user_u -r s0 -R sysadm_r john
>>
> -R doesn't actually work. It can't handle more than one role, and it
> handles that one role incorrectly.
> I agree with what you're saying though...
>
-R "user_r sysadm_t secadm_r"
works or at least should work.
--
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.
next prev parent reply other threads:[~2006-01-20 14:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-20 1:09 [SEMANAGE] Further bugfixes Ivan Gyurdiev
2006-01-20 12:20 ` Russell Coker
2006-01-20 12:34 ` Ivan Gyurdiev
2006-01-20 14:03 ` Daniel J Walsh [this message]
2006-01-20 14:08 ` Ivan Gyurdiev
2006-01-20 14:39 ` Russell Coker
2006-01-20 15:28 ` Stephen Smalley
2006-01-20 14:22 ` Russell Coker
2006-01-20 13:09 ` Stephen Smalley
2006-01-20 14:23 ` Daniel J Walsh
2006-01-20 15:21 ` Stephen Smalley
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=43D0EDA1.5070002@redhat.com \
--to=dwalsh@redhat.com \
--cc=SELinux@tycho.nsa.gov \
--cc=ivg2@cornell.edu \
--cc=russell@coker.com.au \
--cc=sds@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.