selinux-refpolicy.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Burgener, Daniel" <dburgener@tresys.com>
To: "selinux-refpolicy@vger.kernel.org"  <selinux-refpolicy@vger.kernel.org>
Subject: SELint
Date: Thu, 16 Jan 2020 14:37:34 +0000	[thread overview]
Message-ID: <53806485-18fe-0cd8-ca16-9cdb495cdb92@tresys.com> (raw)

Hello,

We have created a tool a that I think people on this list may find very
useful as they do refpolicy related work.  It's called SELint and does
static code analysis on refpolicy style SELinux policy.  You can find
the tool on our git repo here:

https://github.com/TresysTechnology/selint

It currently has 13 checks for common policy issues, and we hope to add
more going forward.

I submitted a pull request to the refpolicy github this morning that
fixes some of the issues reported by the tool, and hope to continue
submitting more over the next few days.

-Daniel

             reply	other threads:[~2020-01-16 14:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-16 14:37 Burgener, Daniel [this message]
2020-01-16 19:52 ` [Non-DoD Source] SELint jwcart2

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=53806485-18fe-0cd8-ca16-9cdb495cdb92@tresys.com \
    --to=dburgener@tresys.com \
    --cc=selinux-refpolicy@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).