From: "EZ" <papaz@md.prestige.net>
To: "ipv6" <ipv6@311c.com>, "Stephen Smalley" <sds@tislabs.com>,
"Frank Mayer" <mayerf@tresys.com>
Cc: <SELinux@tycho.nsa.gov>
Subject: Re: Security policy analysis
Date: Wed, 10 Oct 2001 13:52:24 -0400 [thread overview]
Message-ID: <002c01c151b4$51fe54b0$0500a8c0@winpro2000> (raw)
In-Reply-To: 000b01c15197$1b5ee540$ce164318@servers23.com
Same here...a copy would be great!
Edmund Zynda II
----- Original Message -----
From: "ipv6" <ipv6@311c.com>
To: "Stephen Smalley" <sds@tislabs.com>; "Frank Mayer" <mayerf@tresys.com>
Cc: <SELinux@tycho.nsa.gov>
Sent: Wednesday, October 10, 2001 10:23 AM
Subject: Re: Security policy analysis
>
>
>
> >
> > On Tue, 9 Oct 2001, Frank Mayer wrote:
> >
> > > We also find ourselves incrementally building tools to analyze
> policy.conf
> > > files (e.g., show all types with a given attribute, show all rules
that
> > > involve a given type/attribute). Essentially to help reverse engineer
> and
> > > analyze the intent of a given policy. We have some capabilities
built,
> and
> > > are writing additional ones as time and need allow (essentially by
> borrowing
> > > the lex/yacc source from checkpolicy, and building our own policy
> database
> > > and analysis logic). Is anyone else building similar tools? We'd be
> happy
> > > to share our source incrementally with members of the list as we build
> new
> > > capabilities if anyone is interested.
>
> > We're interested in the capabilities that you've developed. Can we
> > acquire a copy?
>
> We would also like to get a copy if that is possible?
>
> Joop Cousteau
> CTO
> ImageSave Corp
>
>
>
> --
> You have received this message because you are subscribed to the selinux
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.
--
You have received this message because you are subscribed to the selinux 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:[~2001-10-10 17:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-09 19:49 Security policy analysis Frank Mayer
2001-10-09 23:32 ` John Scroggins
2001-10-10 6:05 ` Interested in Reserach work Ravi Prakash B.V.
2001-10-10 12:26 ` Security policy analysis Stephen Smalley
2001-10-10 14:23 ` ipv6
2001-10-10 14:39 ` Frank Mayer
2001-10-10 12:50 ` Julien Palardy
2001-10-10 17:52 ` EZ [this message]
2001-10-10 19:40 ` ipv6
2001-10-10 17:02 ` Jon Crowley
2001-10-10 18:09 ` Frank Mayer
2001-10-10 19:32 ` Stephen Smalley
2001-10-10 20:11 ` Frank Mayer
2001-10-10 21:11 ` Frank Mayer
2001-10-10 20:11 ` Frank Mayer
2001-10-10 19:04 ` 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='002c01c151b4$51fe54b0$0500a8c0@winpro2000' \
--to=papaz@md.prestige.net \
--cc=SELinux@tycho.nsa.gov \
--cc=ipv6@311c.com \
--cc=mayerf@tresys.com \
--cc=sds@tislabs.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.