From: Alexey Dobriyan <adobriyan@gmail.com>
To: Christian Kujau <lists@nerdbynature.de>
Cc: Kees Cook <keescook@chromium.org>,
Andrew Morton <akpm@linux-foundation.org>,
Willy Tarreau <w@1wt.eu>,
Dan Carpenter <dan.carpenter@oracle.com>,
linux-kernel@vger.kernel.org
Subject: Re: process '/usr/bin/rsync' started with executable stack
Date: Wed, 24 Jun 2020 00:45:40 +0300 [thread overview]
Message-ID: <20200623214540.GA42941@localhost.localdomain> (raw)
In-Reply-To: <alpine.DEB.2.22.1.446.2006231430280.3892@trent.utfs.org>
On Tue, Jun 23, 2020 at 02:33:50PM -0700, Christian Kujau wrote:
> On Tue, 23 Jun 2020, Kees Cook wrote:
> > > $ checksec --format=json --extended --file=`which rsync` | jq
> > > {
> > > "/usr/bin/rsync": {
> > > "relro": "full",
> > > "canary": "yes",
> > > "nx": "no",
> > ^^^^^^^^^^^^^^^^^^
> >
> > It is, indeed, marked executable, it seems. What distro is this?
>
> Arch Linux (x86-64) with 5.6.5.a-1-hardened[0], running in a Xen DomU.
>
> Christian.
>
> [0] https://git.archlinux.org/svntogit/packages.git/tree/trunk?h=packages/linux-hardened
Fixed in testing (rsync-3.2.1-1-x86_64.pkg)
GNU_STACK 0x0000000000000000 0x0000000000000000 0x0000000000000000
0x0000000000000000 0x0000000000000000 RW 0x10
next prev parent reply other threads:[~2020-06-23 21:45 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 [this message]
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
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=20200623214540.GA42941@localhost.localdomain \
--to=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=dan.carpenter@oracle.com \
--cc=keescook@chromium.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox