From: "shintarou_fujiwara" <shin216@xf7.so-net.ne.jp>
To: "Stephen Smalley" <sds@tycho.nsa.gov>
Cc: "selinux mailing list" <selinux@tycho.nsa.gov>
Subject: Re: I've written a shell script which turns log deny to allow.
Date: Thu, 6 Oct 2005 06:04:36 +0900 [thread overview]
Message-ID: <004201c5c9f0$64d74250$0300a8c0@admin0> (raw)
In-Reply-To: 1128522649.24059.148.camel@moss-spartans.epoch.ncsc.mil
To Mr Stephen Smalley:
Thank you very much letting me know more sophisticated
policy generator.
I did not know polgen . The idea is great.
That's exactly what I want to do.
I will check the web page.
Thanks.
Bye.
----- Original Message -----
From: "Stephen Smalley" <sds@tycho.nsa.gov>
To: "shintarou_fujiwara" <shin216@xf7.so-net.ne.jp>
Cc: "John Ramsdell" <ramsdell@mitre.org>; "Brian T. Sniffen"
<bsniffen@mitre.org>; "selinux mailing list" <selinux@tycho.nsa.gov>
Sent: Wednesday, October 05, 2005 11:30 PM
Subject: Re: I've written a shell script which turns log deny to allow.
> On Wed, 2005-10-05 at 23:04 +0900, shintarou_fujiwara wrote:
>> Hello, again from Japan .
>>
>> The other day I've written a policy, noip but
>> today I've written a script , easy to use
>> especially begginers, like me ...
>>
>> Denied log is so annoying , so I've written down this
>> small script named sepolf (selinux policy finder).
>>
>> I really want it to display macro, but all I can do now
>> is to display allow... like audit2allow (I have never used,though).
>>
>> Experts advice I really want to get ,to make it better.
>
> How does it differ from audit2allow? If you think audit2allow lacks
> something, feel free to propose a patch to it.
>
> If you are interested in more sophisticated policy generation, I'd
> suggest that you take a look at polgen. There should be an updated
> release of it soon, but you can look at the polgen 1.1 release from
> http://www.mitre.org/tech/selinux/. Unlike audit2allow, polgen can
> generate new domains and types, recognize patterns and suggest
> appropriate policy, and emit macro-based rules rather than just raw TE
> rules. Note that polgen uses filtered strace output (extended to
> include security contexts) from running the program rather than audit
> messages as its input. This has advantages (e.g. program-specific data,
> more detailed data than one can currently obtain from audit messages)
> and disadvantages (e.g. weak linkage with actual SELinux permission
> checks, lack of data on other processes interacting with the program,
> dependency on patched strace program - which is included in the polgen
> tarball).
>
> --
> Stephen Smalley
> National Security Agency
>
>
> --
> 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.
>
--
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.
prev parent reply other threads:[~2005-10-05 21:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-05 14:04 I've written a shell script which turns log deny to allow shintarou_fujiwara
2005-10-05 14:30 ` Stephen Smalley
2005-10-05 21:04 ` shintarou_fujiwara [this message]
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='004201c5c9f0$64d74250$0300a8c0@admin0' \
--to=shin216@xf7.so-net.ne.jp \
--cc=sds@tycho.nsa.gov \
--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.