From: Tom Horsley <horsley1953@gmail.com>
To: Laura Abbott <labbott@redhat.com>
Cc: linux-kernel@vger.kernel.org, Kees Cook <keescook@chromium.org>,
David Howells <dhowells@redhat.com>,
Serge Hallyn <serge@hallyn.com>,
James Morris <james.l.morris@oracle.com>
Subject: Re: ptrace versus setuid changes in 4.14?
Date: Fri, 22 Dec 2017 15:55:36 -0500 [thread overview]
Message-ID: <20171222155536.502c0a53@zooty> (raw)
In-Reply-To: <ddbb8e2e-895e-8377-ed02-8950404e9708@redhat.com>
On Fri, 22 Dec 2017 12:28:25 -0800
Laura Abbott wrote:
> Assuming this is https://bugzilla.redhat.com/show_bug.cgi?id=1528633
> This is yet another victim of
>
> commit e37fdb785a5f95ecadf43b773c97f676500ac7b8 (refs/bisect/bad)
> Author: Kees Cook <keescook@chromium.org>
> Date: Tue Jul 18 15:25:31 2017 -0700
>
> exec: Use secureexec for setting dumpability
You mean there is hope this really is a bug and not a security
enhancement? Amazing :-).
And yes, that is the bugzilla I submitted after I reduced
things to a small test program.
next prev parent reply other threads:[~2017-12-22 20:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-21 14:18 ptrace versus setuid changes in 4.14? Tom Horsley
2017-12-22 20:28 ` Laura Abbott
2017-12-22 20:55 ` Tom Horsley [this message]
2017-12-22 23:14 ` 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=20171222155536.502c0a53@zooty \
--to=horsley1953@gmail.com \
--cc=dhowells@redhat.com \
--cc=james.l.morris@oracle.com \
--cc=keescook@chromium.org \
--cc=labbott@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=serge@hallyn.com \
/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