linux-kernel - Re: [PATCH 0/4] KEYS: validate key trust with owner and builtin keys only

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-next>] [day] [month] [year] [list]

Message-ID: <20140610204021.GA8916@srcf.ucam.org>
Date:	Tue, 10 Jun 2014 21:40:21 +0100
From:	Matthew Garrett <mjg59@...f.ucam.org>
To:	Dmitry Kasatkin <dmitry.kasatkin@...il.com>
Cc:	Josh Boyer <jwboyer@...hat.com>,
	David Howells <dhowells@...hat.com>,
	Mimi Zohar <zohar@...ux.vnet.ibm.com>,
	Dmitry Kasatkin <d.kasatkin@...sung.com>,
	keyrings@...ux-nfs.org, linux-kernel@...r.kernel.org,
	linux-security-module@...r.kernel.org
Subject: Re: [PATCH 0/4] KEYS: validate key trust with owner and builtin keys
 only

On Tue, Jun 10, 2014 at 11:34:17PM +0300, Dmitry Kasatkin wrote:

> Preventing loading keys from uefi except dbx by default actually improves
> security. Adding kernel parameter to read db we make system more
> vulnerable.

It only adds security if you're performing a measured boot and remote 
attestation. Otherwise you implicitly trust that key anyway. In almost 
all cases refusing to trust db gives you a false sense of security 
without any real improvement. I don't think it's obvious it should be 
the default.

-- 
Matthew Garrett | mjg59@...f.ucam.org
--
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/