All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tim Brown <tmb@65535.com>
To: kernel-hardening@lists.openwall.com
Cc: Corey Bryant <coreyb@linux.vnet.ibm.com>,
	oss-security@lists.openwall.com
Subject: Re: [kernel-hardening] Security vulnerability tools
Date: Wed, 27 Mar 2013 19:58:38 +0000	[thread overview]
Message-ID: <201303271958.46601.tmb@65535.com> (raw)
In-Reply-To: <51534E5C.8070303@linux.vnet.ibm.com>

[-- Attachment #1: Type: Text/Plain, Size: 1294 bytes --]

On Wednesday 27 Mar 2013 19:54:04 Corey Bryant wrote:
> Hi,
> 
> I'd like to get a better understanding of tools used in the open source
> community (kernel and user space) to detect security vulnerabilities.
> 
> I have a list below to get started.  If anyone has any input, I'd
> appreciate it!
> 
> I'll plan on updating http://oss-security.openwall.org/wiki/tools with
> anything it doesn't already have.
> 

Hey Corey,

One you might want to add is unix-privesc-check from myself, @inquisb and 
@pentestmonkey.  There are two versions in existence:

1.x - @pentestmonkey's quick and dirty with some hacks by me
trunk - a full blown privesc check framework designed by me with contributions 
from the other two, it has multiple modes of operation, a standard library 
which can be leveraged for new checks and (already) enhanced capabilities.   
Its not perfect yet, I still need to clean it up and port it to the commercial 
UNIX platforms we support but it should give a good idea of where we're going

Once I've stabilised the API of trunk, it will become 2.x and we'll open it up 
formerly for contributions.

It's on Google Code if people want to take a look:

* http://code.google.com/p/unix-privesc-check

Tim
-- 
Tim Brown
<mailto:tmb@65535.com>

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2013-03-27 19:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-27 19:54 [kernel-hardening] Security vulnerability tools Corey Bryant
2013-03-27 19:58 ` Tim Brown [this message]
2013-03-27 20:12 ` [kernel-hardening] " Solar Designer
2013-03-27 21:17   ` Corey Bryant
2013-03-28  7:32     ` Solar Designer
2013-04-08  5:37       ` Hasinoliva MIARIMANJATO
2013-03-27 20:31 ` [kernel-hardening] Re: [oss-security] " Russ Allbery

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=201303271958.46601.tmb@65535.com \
    --to=tmb@65535.com \
    --cc=coreyb@linux.vnet.ibm.com \
    --cc=kernel-hardening@lists.openwall.com \
    --cc=oss-security@lists.openwall.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.