lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20131213002523.GA20706@redhat.com>
Date:	Thu, 12 Dec 2013 19:25:23 -0500
From:	Dave Jones <davej@...hat.com>
To:	Kees Cook <keescook@...omium.org>
Cc:	"Theodore Ts'o" <tytso@....edu>, vegard.nossum@...cle.com,
	LKML <linux-kernel@...r.kernel.org>,
	Tommi Rantala <tt.rantala@...il.com>,
	Ingo Molnar <mingo@...nel.org>,
	"Eric W. Biederman" <ebiederm@...ssion.com>,
	Andy Lutomirski <luto@...capital.net>,
	Daniel Vetter <daniel.vetter@...ll.ch>,
	Alan Cox <alan@...ux.intel.com>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Jason Wang <jasowang@...hat.com>,
	"David S. Miller" <davem@...emloft.net>,
	Dan Carpenter <dan.carpenter@...cle.com>,
	James Morris <james.l.morris@...cle.com>
Subject: Re: [PATCH 1/9] Known exploit detection

On Thu, Dec 12, 2013 at 01:13:41PM -0800, Kees Cook wrote:

 > - who will keep adding these triggers going forward?

also..

- Who will test the existing triggers are doing the right thing when related code changes.

We could add something to tests/ maybe for each exploit() addition, to make sure some
new change isn't introducing an oopsable (or worse!) bug in the actual exploit test.

It does mean someone needs to be regularly running said tests though.
As history has shown, things like nx_test have been broken for months at a time without
anyone complaining.  Perhaps Fenguang Wu can add something to the daily test runs if
we add an over all "make test-secure" target or similar.

	Dave

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ