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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Fri, 1 Mar 2013 00:52:51 +0100 (CET)
From:	Jiri Kosina <jkosina@...e.cz>
To:	Matthew Garrett <mjg59@...f.ucam.org>
Cc:	David Howells <dhowells@...hat.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	jwboyer@...hat.com, pjones@...hat.com, vgoyal@...hat.com,
	keescook@...omium.org, keyrings@...ux-nfs.org,
	linux-kernel@...r.kernel.org, Greg KH <gregkh@...uxfoundation.org>,
	Florian Weimer <fw@...eb.enyo.de>,
	Paolo Bonzini <pbonzini@...hat.com>
Subject: Re: [GIT PULL] Load keys from signed PE binaries

On Thu, 28 Feb 2013, Matthew Garrett wrote:

> > > Sure, if you've been infected before the revocation, you'll still be 
> > > infected. There's not really any good way around that.
> > 
> > Which is a very substantial difference to normal X509 chain of trust, 
> > isn't it?
> 
> If you've loaded an x.509 certificate into the kernel and it's later 
> revoked, any module signed with the key is going to be loadable until 
> it's revoked. I don't see an especially large difference here?

i_own_your_ring0.ko can be modprobed long after blacklisting of "hello 
world" binary hash has happened on the very particular machine in its dbx 
(as there is no link, in a x509-chain-of-trust-sense, between the hash of 
the PE binary and the i_own_your_ring0.ko signature key).

modprobe of a module signed by a key that has been blacklisted on the very 
particular machine in its dbx is not going to work (as there is a very 
direct x509 chain of trust link).

No?

Thanks,

-- 
Jiri Kosina
SUSE Labs
--
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