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: <20140610150848.GB7551@srcf.ucam.org>
Date:	Tue, 10 Jun 2014 16:08:48 +0100
From:	Matthew Garrett <mjg59@...f.ucam.org>
To:	Dmitry Kasatkin <d.kasatkin@...sung.com>
Cc:	Josh Boyer <jwboyer@...hat.com>, zohar@...ux.vnet.ibm.com,
	dhowells@...hat.com, keyrings@...ux-nfs.org,
	linux-security-module@...r.kernel.org,
	linux-kernel@...r.kernel.org, dmitry.kasatkin@...il.com
Subject: Re: [PATCH 0/4] KEYS: validate key trust with owner and builtin keys
 only

On Tue, Jun 10, 2014 at 03:58:54PM +0300, Dmitry Kasatkin wrote:

> It is tricky issue. But yes and no... If I forced to trust MS key to run
> SHIM, it does not mean
> that I want to trust MS key to run kernel and load modules or use MS key
> to valid other keys on system keyring.

A kernel parameter that refuses to trust the contents of DB would be 
acceptable, but DBX needs to be used unconditionally.

-- 
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ