linux-kernel - Re: [PATCH 0/4] MSR: MSR: MSR Whitelist and Batch Introduction

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: <20160301183839.GC22677@pd.tnic>
Date:	Tue, 1 Mar 2016 19:38:39 +0100
From:	Borislav Petkov <bp@...en8.de>
To:	"Rountree, Barry L." <rountree4@...l.gov>
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	George Spelvin <linux@...izon.com>,
	"a.p.zijlstra@...llo.nl" <a.p.zijlstra@...llo.nl>,
	"acme@...radead.org" <acme@...radead.org>,
	"ak@...ux.intel.com" <ak@...ux.intel.com>,
	"andriy.shevchenko@...ux.intel.com" 
	<andriy.shevchenko@...ux.intel.com>,
	"brgerst@...il.com" <brgerst@...il.com>,
	"dan.j.williams@...el.com" <dan.j.williams@...el.com>,
	"dyoung@...hat.com" <dyoung@...hat.com>,
	"hpa@...or.com" <hpa@...or.com>,
	"jolsa@...hat.com" <jolsa@...hat.com>,
	"Mcfadden, Marty Jay" <mcfadden8@...l.gov>,
	"luto@...nel.org" <luto@...nel.org>,
	"mingo@...nel.org" <mingo@...nel.org>,
	"mingo@...hat.com" <mingo@...hat.com>,
	"pavel@....cz" <pavel@....cz>,
	"viro@...iv.linux.org.uk" <viro@...iv.linux.org.uk>,
	"x86@...nel.org" <x86@...nel.org>,
	"yu.c.chen@...el.com" <yu.c.chen@...el.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Travis Gummels <tgummels@...hat.com>,
	"Eastep, Jonathan M" <jonathan.m.eastep@...el.com>,
	"len.brown@...el.com" <len.brown@...el.com>,
	"prarit@...hat.com" <prarit@...hat.com>
Subject: Re: [PATCH 0/4] MSR: MSR: MSR Whitelist and Batch Introduction

On Tue, Mar 01, 2016 at 06:29:59PM +0000, Rountree, Barry L. wrote:

> ... And we can provide this access on production machines without
> risking inadvertent or malicious scribbling on non-benign MSRs. And we
> can do this with one simple, straightforward kernel module.

So you can simply keep that module in your repo and apply it each time
before doing a security review. It is not meant for upstream use anyway.

-- 
Regards/Gruss,
    Boris.

ECO tip #101: Trim your mails when you reply.