From: Daniel J Walsh <dwalsh@redhat.com>
To: Tom <tom@lemuria.org>
Cc: selinux@tycho.nsa.gov
Subject: Re: SELinux question?
Date: Tue, 04 Feb 2003 10:49:03 -0500 [thread overview]
Message-ID: <3E3FE0EF.8030105@redhat.com> (raw)
In-Reply-To: <20030204154613.A7115@lemuria.org>
[-- Attachment #1: Type: text/plain, Size: 857 bytes --]
Tom wrote:
>On Tue, Feb 04, 2003 at 02:58:38AM -0500, Daniel J Walsh wrote:
>
>
>>Why are certain applications (ls, cp, cd) ported to use SELinux with the
>>standard names, while others
>>(spasswd, schfn) have a prefix added?
>>
>>
>
>ls, ps and others are modified versions of the originals.
>
>spasswd, and the other s* programs are wrappers around the original
>tools. For various reasons, this was the only or better way of making
>them SE-aware in those cases.
>
>
>
>
>
So they did it because it was easier to wrap the application then to
change the code, correct?
In the other cases they could not wrap the apps so they went in and
changed the code.
I would like to know if there was any other reason to use the s* syntax,
or all things being equil
you would replace the passwd command with a SELinux aware passwd command?
Dan
Dan
[-- Attachment #2: Type: text/html, Size: 1191 bytes --]
next prev parent reply other threads:[~2003-02-04 15:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-27 13:20 tmpfs_t Stephen D. Smalley
2003-02-01 22:51 ` tmpfs_t Russell Coker
2003-02-04 7:58 ` SELinux question? Daniel J Walsh
2003-02-04 14:46 ` Tom
2003-02-04 15:49 ` Daniel J Walsh [this message]
2003-02-04 16:31 ` Russell Coker
2003-02-04 16:51 ` Frank Mayer
-- strict thread matches above, loose matches on Subject: below --
2003-02-04 17:21 Stephen D. 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=3E3FE0EF.8030105@redhat.com \
--to=dwalsh@redhat.com \
--cc=selinux@tycho.nsa.gov \
--cc=tom@lemuria.org \
/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.