From: Christian Kujau <lists@nerdbynature.de>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Willy Tarreau <w@1wt.eu>,
Dan Carpenter <dan.carpenter@oracle.com>,
Kees Kook <keescook@chromium.org>,
linux-kernel@vger.kernel.org
Subject: Re: process '/usr/bin/rsync' started with executable stack
Date: Tue, 23 Jun 2020 14:51:55 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.22.1.446.2006231435450.3892@trent.utfs.org> (raw)
In-Reply-To: <20200623212214.GA41702@localhost.localdomain>
On Wed, 24 Jun 2020, Alexey Dobriyan wrote:
> > > process '/usr/bin/rsync' started with executable stack
> > > But I can't reproduce this message,
>
> This message is once-per-reboot.
Interesting, thanks. Now I know why I cannot reproduce this. I still
wonder what made rsync trigger this message today. The machine is running
for some weeks, rsync is run a few times an hour the whole day, regularly
and automatically, with always the same parameters. But oh, now I see,
rsync had been upgraded (automatically) over night:
> [ALPM] upgraded rsync (3.1.3-3 -> 3.2.0-1)
And indeed, the _older_ version had NX enabled:
$ wget https://archive.archlinux.org/packages/.all/rsync-3.1.3-3-x86_64.pkg.tar.zst
$ zstd -dc rsync-3.1.3-3-x86_64.pkg.tar.zst | tar -xf - usr/bin/rsync
$ checksec --format=json --extended --file=usr/bin/rsync | jq
{
"usr/bin/rsync": {
"relro": "full",
"canary": "yes",
"nx": "yes",
"pie": "yes",
"clangcfi": "no",
"safestack": "no",
"rpath": "no",
"runpath": "no",
"symbols": "no",
"fortify_source": "yes",
"fortified": "10",
"fortify-able": "19"
}
}
So, while I still think a PID would have been nice, now I know that it's
pr_warn_once and won't be printed again until after the next reboot. Going
to ask the Arch folks why NX has been disabled...
Thanks,
Christian.
--
BOFH excuse #211:
Lightning strikes.
next prev parent reply other threads:[~2020-06-23 21:52 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 [this message]
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=alpine.DEB.2.22.1.446.2006231435450.3892@trent.utfs.org \
--to=lists@nerdbynature.de \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=dan.carpenter@oracle.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).