linux-kernel - Re: [PATCH 0/10] Add additional security checks when module loading is restricted

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: <1377731577.27493.11.camel@x230>
Date:	Wed, 28 Aug 2013 23:12:57 +0000
From:	Matthew Garrett <matthew.garrett@...ula.com>
To:	Kees Cook <keescook@...omium.org>
CC:	Lenny Szubowicz <lszubowi@...hat.com>,
	LKML <linux-kernel@...r.kernel.org>,
	"linux-efi@...r.kernel.org" <linux-efi@...r.kernel.org>,
	Josh Boyer <jwboyer@...hat.com>
Subject: Re: [PATCH 0/10] Add additional security checks when module loading
 is restricted

On Wed, 2013-08-28 at 16:07 -0700, Kees Cook wrote:

> Strictly speaking, RAM contents are not available via /dev/*mem, even
> to root. However, you can request a suspend image be written, but to
> not enter hibernation. Then modify the image, and request a resume
> from it.

Is that true? Oh, hm - I guess you could do it with uswsusp. Ugh. Now I
wonder what else you can do with uswsusp. Yeah, ok, I think that case
certainly needs handling.

-- 
Matthew Garrett <matthew.garrett@...ula.com>