All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dale Amon <amon@vnl.com>
To: Karl MacMillan <kmacmillan@tresys.com>
Cc: SELinux List <SELinux@tycho.nsa.gov>
Subject: Re: Setools 1.0.1 released
Date: Fri, 7 Nov 2003 13:15:19 +0000	[thread overview]
Message-ID: <20031107131519.GF22435@vnl.com> (raw)
In-Reply-To: <1067890582.1269.32.camel@colossus.columbia.tresys.com>

On Mon, Nov 03, 2003 at 03:16:22PM -0500, Karl MacMillan wrote:
> We have just released version 1.0.1 of setools. This is a minor update

Karl, I've not used your tools yet because I'm only
working with selinux on servers and firewalls with 
minimal package sets, ie no X. 

Do your tools allow study of policy files on the
non-selinux build system? Or are there command line
tools useable directly on the target system?

-- 
------------------------------------------------------
       IN MY NAME:            Dale Amon, CEO/MD
  No Mushroom clouds over     Islandone Society
    London and New York.      www.islandone.org
------------------------------------------------------

--
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.

  parent reply	other threads:[~2003-11-07 13:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-03 20:16 Setools 1.0.1 released Karl MacMillan
2003-11-04  0:54 ` GDM and PAM problems? Richard Herbert Wanner
2003-11-04  4:13   ` Daniel J Walsh
2003-11-04 13:46 ` Setools 1.0.1 released Karl MacMillan
2003-11-07 13:15 ` Dale Amon [this message]
2003-11-07 16:21   ` Karl MacMillan
2003-11-07 21:23     ` Dale Amon
2003-11-14 15:04 ` GNU Coding Standards (was: Setools 1.0.1 released) John D. Ramsdell
2003-11-14 17:03   ` Karl MacMillan
2003-11-14 18:23   ` GNU Coding Standards gndeva
2003-11-14 21:48     ` Russell Coker

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=20031107131519.GF22435@vnl.com \
    --to=amon@vnl.com \
    --cc=SELinux@tycho.nsa.gov \
    --cc=kmacmillan@tresys.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.