From: "H. Peter Anvin" <hpa@zytor.com>
To: Andy Lutomirski <luto@amacapital.net>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Julien Tinnes <jln@google.com>,
David Drysdale <drysdale@google.com>,
Al Viro <viro@zeniv.linux.org.uk>,
Paolo Bonzini <pbonzini@redhat.com>,
LSM List <linux-security-module@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Paul Moore <paul@paul-moore.com>,
James Morris <james.l.morris@oracle.com>,
Linux API <linux-api@vger.kernel.org>,
Meredydd Luff <meredydd@senatehouse.org>,
Christoph Hellwig <hch@infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Kees Cook <keescook@chromium.org>,
"Theodore Ts'o" <tytso@mit.edu>,
Henrique de Moraes Holschuh <hmh@hmh.eng.br>,
linux-crypto@vger.kernel.org
Subject: Re: General flags to turn things off (getrandom, pid lookup, etc)
Date: Fri, 25 Jul 2014 16:43:20 -0700 [thread overview]
Message-ID: <53D2EB98.3090802@zytor.com> (raw)
In-Reply-To: <CALCETrWGvBfrX1W5XaFgJZhKHLf+oac9YrwPR3ppK=deQtu5hA@mail.gmail.com>
On 07/25/2014 11:30 AM, Andy Lutomirski wrote:
> - 32-bit GDT code segments [huge attack surface]
> - 64-bit GDT code segments [probably pointless]
I presume you mean s/GDT/LDT/.
We already don't allow 64-bit LDT code segments. Also, it is unclear to
me how 32-bit LDT segments have a huge attack surface, given that there
will realistically always be a 32-bit *GDT* segment present.
-hpa
next prev parent reply other threads:[~2014-07-25 23:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-25 18:30 General flags to turn things off (getrandom, pid lookup, etc) Andy Lutomirski
2014-07-25 20:15 ` Dave Jones
2014-07-25 20:21 ` Andy Lutomirski
2014-07-25 21:35 ` One Thousand Gnomes
2014-07-25 21:41 ` Andy Lutomirski
2014-07-26 19:48 ` Eric W. Biederman
2014-07-30 14:37 ` One Thousand Gnomes
2014-07-25 23:43 ` H. Peter Anvin [this message]
2014-07-25 23:54 ` Andy Lutomirski
2014-07-27 12:26 ` David Drysdale
2014-07-27 21:06 ` Theodore Ts'o
2014-07-27 22:17 ` Andy Lutomirski
2014-07-27 23:53 ` Eric W. Biederman
2014-07-30 14:37 ` One Thousand Gnomes
2014-07-30 18:41 ` Eric W. Biederman
2014-07-30 21:29 ` One Thousand Gnomes
2014-07-31 2:37 ` Eric W. Biederman
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=53D2EB98.3090802@zytor.com \
--to=hpa@zytor.com \
--cc=drysdale@google.com \
--cc=ebiederm@xmission.com \
--cc=gregkh@linuxfoundation.org \
--cc=hch@infradead.org \
--cc=hmh@hmh.eng.br \
--cc=james.l.morris@oracle.com \
--cc=jln@google.com \
--cc=keescook@chromium.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=meredydd@senatehouse.org \
--cc=paul@paul-moore.com \
--cc=pbonzini@redhat.com \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
/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