public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kees Cook <keescook@chromium.org>
To: Thorsten Glaser <tg@debian.org>
Cc: Dan Carpenter <dan.carpenter@oracle.com>,
	Ben Hutchings <ben@decadent.org.uk>,
	Christian Kujau <lists@nerdbynature.de>,
	Alexey Dobriyan <adobriyan@gmail.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Willy Tarreau <w@1wt.eu>,
	linux-kernel@vger.kernel.org, klibc@lists.zytor.com,
	"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [klibc] process '/usr/bin/rsync' started with executable stack
Date: Thu, 25 Jun 2020 15:01:31 -0700	[thread overview]
Message-ID: <202006251458.91D1E27A@keescook> (raw)
In-Reply-To: <Pine.BSM.4.64L.2006252115450.4838@herc.mirbsd.org>

On Thu, Jun 25, 2020 at 09:16:10PM +0000, Thorsten Glaser wrote:
> Kees Cook dixit:
> 
> >3) fix the use of trampolines in klibc
> 
> AIUI done in klibc, but post-2.0.7

Ah-ha, I see it. Ben got it fixed in Feb. :)

https://git.kernel.org/pub/scm/libs/klibc/klibc.git/commit/?id=9d8d648e604026b32cad00a84ed6c29cbd157641

I don't see it in Debian? I remain confused, but there's hope!
https://salsa.debian.org/kernel-team/klibc/-/commits/master

-- 
Kees Cook

  reply	other threads:[~2020-06-25 22:01 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-23 17:39 process '/usr/bin/rsync' started with executable stack Christian Kujau
2020-06-23 18:32 ` Kees Cook
2020-06-23 21:33   ` Christian Kujau
2020-06-23 21:41     ` Alexey Dobriyan
2020-06-23 21:45     ` Alexey Dobriyan
2020-06-23 21:50     ` Alexey Dobriyan
2020-06-23 22:02       ` Christian Kujau
2020-06-23 21:12 ` Alexey Dobriyan
2020-06-23 21:22   ` Alexey Dobriyan
2020-06-23 21:51     ` Christian Kujau
2020-06-23 23:20     ` Kees Cook
2020-06-24  5:34       ` Christian Kujau
2020-06-24 16:51 ` Dan Carpenter
2020-06-24 19:39   ` Kees Cook
2020-06-25 10:04     ` Dan Carpenter
2020-06-25 20:20       ` Kees Cook
2020-06-25 21:16         ` [klibc] " Thorsten Glaser
2020-06-25 22:01           ` Kees Cook [this message]
2020-06-26  4:42         ` Christophe Leroy
2020-07-25 21:27         ` Ben Hutchings
2020-07-26  2:07           ` Kees Cook

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=202006251458.91D1E27A@keescook \
    --to=keescook@chromium.org \
    --cc=adobriyan@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=ben@decadent.org.uk \
    --cc=dan.carpenter@oracle.com \
    --cc=hpa@zytor.com \
    --cc=klibc@lists.zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lists@nerdbynature.de \
    --cc=tg@debian.org \
    --cc=w@1wt.eu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox