linux-kernel - Re: + signal-always-clear-sa_restorer-on-execve.patch added to -mm tree

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

Date:	Mon, 11 Mar 2013 14:42:34 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Kees Cook <keescook@...omium.org>
Cc:	Greg KH <gregkh@...uxfoundation.org>,
	Ben Hutchings <ben@...adent.org.uk>,
	Luis Henriques <luis.henriques@...onical.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Julien Tinnes <jln@...gle.com>,
	PaX Team <pageexec@...email.hu>,
	Emese Revfy <re.emese@...il.com>
Subject: Re: + signal-always-clear-sa_restorer-on-execve.patch added to -mm
 tree

On Mon, 11 Mar 2013 14:33:18 -0700 Kees Cook <keescook@...omium.org> wrote:

> > patch #1: use SA_RESTORER, cc stable (please promise me this will work OK)
> 
> I don't have the ability to build all the architectures, but it seems
> like the best flag based on code review.

SA_RESTORER looks OK back to 3.5 (at least).

> > patch #2: switch to __ARCH_HAS_SA_RESTORER, no cc stable
> >
> > I'm assuming this is all for 3.10, btw.  If you think it should be in
> > 3.9 then you need to write scarier changelogs.
> 
> Well, I'm not sure it needs to be scarier; it's a serious local ASLR
> info leak. I was hoping it could go into 3.9 since the expectation is
> for it to go to stable, so why not put it in 3.9 now?

OK.

> Do you want me to spin up the 2-patch solution or is it too much of a hack?

Is OK, I have it all lined up.
--
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/