From: Albert Cahalan <albert@users.sourceforge.net>
To: "Loughry, Joe" <joe.loughry@lmco.com>
Cc: Albert Cahalan <albert@users.sourceforge.net>, SELinux@tycho.nsa.gov
Subject: RE: non-Linux behavior
Date: 29 Dec 2003 11:20:24 -0500 [thread overview]
Message-ID: <1072714824.828.1259.camel@cube> (raw)
In-Reply-To: <835AD41BA2589F49A8A34117D4C421DF02CA1E80@EMSS02M15.us.lmco.com>
On Mon, 2003-12-29 at 12:34, Loughry, Joe wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> I can help out with Trusted Solaris. Which of the following versions
> would you like?
>
> Trusted Solaris 8 HW 7/03 (beta, not yet released)
> Trusted Solaris 8 HW 12/02 (with current patches)
> Trusted Solaris 8 4/01 (with current patches)
> Trusted Solaris 2.5.1 (with current patches)
The very latest one you have. I guess "8 HW 7/03"
would be the latest? Take a glance through the
man page to see if I've missed any recently added
options, then run the commands as I've indicated.
The "script" command may be helpful.
Thank you for the offer.
> - -----Original Message-----
> From: owner-selinux@tycho.nsa.gov
> [mailto:owner-selinux@tycho.nsa.gov]On
> Behalf Of Albert Cahalan
> Sent: Friday, 26 December, 2003 08:41
> To: SELinux@tycho.nsa.gov
> Subject: non-Linux behavior
>
>
> I've been adding SE Linux support to procps.
> The 3.1.15 release supports "--context" when
> run on a 2.6.0 kernel. (http://procps.sf.net/)
>
> I need some help. One of my goals is to be
> mostly compatible with both UNIX and BSD.
> I'm looking for people willing to try out
> security-related ps options on high-security
> systems. Better yet would be a trial account.
>
> I'm interested in whatever systems commonly
> in use or are likely to be of importance.
> I guess that means: Trusted IRIX, Cray's OS,
> Trusted Solaris, FreeBSD with LOMAC, and
> probably stuff from IBM or HP. Anything else?
> If you'd like Linux compatible with whatever
> it is you've been using, speak now.
>
> For those who can help only by typing commands
> themselves, feel free to change command names
> to "[x]", "x", or "x x" as appropriate. (I need
> to know if args are shown or if brakets are used)
> The same goes for user names, etc.
>
> I'd like to have output from at least:
>
> ps -Z
> ps -flZ
> ps -Zlf
> ps -ZelfLyPcj (all the options you can do)
> ps Z
>
> Then again, replacing the 'Z' with 'z'.
> Then again, this time with 'M'.
> Then again, this time with 'x'.
> Then again, this time with 'C'.
> And so on, for every security-related option...
>
> Plus this one:
>
> ps -zMZ (all available security options at once)
>
> The goal here is to determine column width,
> column order, interactions between options, etc.
--
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:[~2003-12-29 16:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-29 17:34 non-Linux behavior Loughry, Joe
2003-12-29 16:20 ` Albert Cahalan [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-12-26 15:41 Albert Cahalan
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=1072714824.828.1259.camel@cube \
--to=albert@users.sourceforge.net \
--cc=SELinux@tycho.nsa.gov \
--cc=joe.loughry@lmco.com \
/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.