linux-kernel - Re: [PATCH 0/3] ELF executable signing and verification

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]

Date:	Wed, 16 Jan 2013 00:17:45 +0100
From:	richard -rw- weinberger <richard.weinberger@...il.com>
To:	Vivek Goyal <vgoyal@...hat.com>
Cc:	linux-kernel@...r.kernel.org, ebiederm@...ssion.com,
	zohar@...ux.vnet.ibm.com, pjones@...hat.com, hpa@...or.com,
	dhowells@...hat.com, jwboyer@...hat.com
Subject: Re: [PATCH 0/3] ELF executable signing and verification

On Wed, Jan 16, 2013 at 12:15 AM, Vivek Goyal <vgoyal@...hat.com> wrote:
> On Tue, Jan 15, 2013 at 11:27:12PM +0100, richard -rw- weinberger wrote:
>> On Tue, Jan 15, 2013 at 10:34 PM, Vivek Goyal <vgoyal@...hat.com> wrote:
>> > Upon exec(), we determine if executable is signed. If it is, then locks
>> > down the pages in memory (using MAP_LOCKED) and verfies the signature.
>> > If signature does not match, process is killed. Unsigned processes
>> > don't get affected at all.
>>
>> Also ptrace() should be disallowed on such a process created from a signed ELF.
>
> Yes, that I have listed in TODO. We need to disable ptrace for signed
> processes or make sure only signed process can trace it.

Memo to myself: Reading long mails on my Android sucks. ;)
I totally missed the TODO section. Sorry for the noise.

-- 
Thanks,
//richard
--
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/