From: "Julien Palardy" <palj@praefect-sys.com>
To: <SELinux@tycho.nsa.gov>
Subject: Re: Security policy analysis
Date: Wed, 10 Oct 2001 14:50:58 +0200 [thread overview]
Message-ID: <005a01c1518a$48fea830$0101000a@praefect> (raw)
In-Reply-To: ACEHIKGIGFEDAIKEMMMIIENFJPAA.mayerf@tresys.com
You have any detail on the licensing form of the code?
I am highly interested in any policy reverse-engineering mechanism, and even
more in policy engineering itself, which can probably be much more useful at
this stage of SELinux's developement.
---
Julien Palardy <palj@praefect-sys.com>
1AC7 1DB0 FEA6 93C2 6731 0AB1 07BA B3C7 458E E234
> I will post a site where the current source can be downloaded within a day
> or two.
>
> However, I still encourage folks who are looking at developing or
analyzing
> security policies to share any insights you might have. Thanks
>
> Frank Mayer
> mayerf@tresys.com
> Tresys Technology
>
--
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 12:50 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 [this message]
2001-10-10 17:52 ` EZ
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='005a01c1518a$48fea830$0101000a@praefect' \
--to=palj@praefect-sys.com \
--cc=SELinux@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.