From: Kees Cook <keescook@chromium.org>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: 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
Subject: Re: process '/usr/bin/rsync' started with executable stack
Date: Wed, 24 Jun 2020 12:39:24 -0700 [thread overview]
Message-ID: <202006241238.E9CB1CE85B@keescook> (raw)
In-Reply-To: <20200624165148.GD31008@kadam>
On Wed, Jun 24, 2020 at 07:51:48PM +0300, Dan Carpenter wrote:
> In Debian testing the initrd triggers the warning.
>
> [ 34.529809] process '/usr/bin/fstype' started with executable stack
Where does fstype come from there? I am going to guess it is either
busybox or linked against klibc?
klibc has known problems with executable stacks due to its trampoline
implementation:
https://wiki.ubuntu.com/SecurityTeam/Roadmap/ExecutableStacks
>
> $ checksec --format=json --extended --file=/var/tmp/mkinitramfs_eTyMPQ/bin/fstype | jq
> {
> "file": {
> "relro": "no",
> "canary": "no",
> "nx": "no",
> "pie": "no",
> "clangcfi": "no",
> "safestack": "no",
> "rpath": "no",
> "runpath": "no",
> "symbols": "no",
> "fortify_source": "no",
> "fortified": "0",
> "fortify-able": "0"
> }
> }
Wow. _nothing_ implemented. :(
--
Kees Cook
next prev parent reply other threads:[~2020-06-24 19:39 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 [this message]
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
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=202006241238.E9CB1CE85B@keescook \
--to=keescook@chromium.org \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=dan.carpenter@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lists@nerdbynature.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.