From: Borislav Petkov <bp@alien8.de>
To: Andy Lutomirski <luto@kernel.org>
Cc: X86 ML <x86@kernel.org>, LKML <linux-kernel@vger.kernel.org>,
Kees Cook <keescook@chromium.org>,
Peter Zijlstra <peterz@infradead.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [RFC] selftests/x86: Add test_vsyscall
Date: Fri, 5 Jan 2018 19:23:54 +0100 [thread overview]
Message-ID: <20180105182354.ishv3rkdsi2fsujs@pd.tnic> (raw)
In-Reply-To: <CALCETrXMSBGM89Ziti-+p71NB6xyXHri1ewJZ50Yt+qw0kbnig@mail.gmail.com>
On Fri, Jan 05, 2018 at 09:53:16AM -0800, Andy Lutomirski wrote:
> emulate_noread would avoid one exploit technique that Kees saw
> somewhere. And per-process disablement would let a system remain
> compatible with old binaries without reducing security for newer
> binaries.
Or we can simply say new binaries can switch to the vdso. Because this
way, vsyscall will never really be phased out - new shit will simply
keep using it.
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
next prev parent reply other threads:[~2018-01-05 18:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-05 5:38 Andy Lutomirski
2018-01-05 12:33 ` Borislav Petkov
2018-01-05 17:53 ` Andy Lutomirski
2018-01-05 18:23 ` Borislav Petkov [this message]
2018-01-05 18:47 ` Andy Lutomirski
2018-01-05 19:05 ` Borislav Petkov
2018-01-05 13:40 ` Borislav Petkov
2018-01-05 18:01 ` Andy Lutomirski
2018-01-05 18:30 ` Borislav Petkov
2018-01-05 18:45 ` Andy Lutomirski
2018-01-05 19:10 ` Borislav Petkov
2018-01-05 19:22 ` Andy Lutomirski
2018-01-05 19:28 ` Borislav Petkov
2018-01-05 20:10 ` Andy Lutomirski
2018-01-09 11:45 ` Naresh Kamboju
2018-01-09 11:51 ` Borislav Petkov
2018-01-09 21:25 ` Shuah Khan
2018-01-09 21:27 ` Andy Lutomirski
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=20180105182354.ishv3rkdsi2fsujs@pd.tnic \
--to=bp@alien8.de \
--cc=gregkh@linuxfoundation.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=peterz@infradead.org \
--cc=x86@kernel.org \
/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
all inboxes | Powered by JetHome®