From: Vasiliy Kulikov <segoon@openwall.com>
To: kernel-hardening@lists.openwall.com
Subject: Re: [kernel-hardening] HARDEN_VM86
Date: Wed, 15 Jun 2011 19:38:45 +0400 [thread overview]
Message-ID: <20110615153845.GA10715@albatros> (raw)
In-Reply-To: <20110615143844.GB32753@openwall.com>
Solar,
On Wed, Jun 15, 2011 at 18:38 +0400, Solar Designer wrote:
> If upstream is fine with sysctl's setting gids, and this appears to be
> the case, then let's go for this.
I see one problem with gid style - as gid is a per pid_namespace thing,
it should be configurable per pid_namespace.
But on the other hand, a potential bug might lead to a privilege
escalation (not a in-namespace root, but e.g. arbitrary write into any
physical address) due to the nature of the syscall. So, in-namespace
root shouldn't be able to configure who is able to do vm86(2), otherwise
it is able to gain full root.
I'm confused :\
--
Vasiliy
next prev parent reply other threads:[~2011-06-15 15:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-14 8:35 [kernel-hardening] HARDEN_VM86 Vasiliy Kulikov
2011-06-15 14:38 ` Solar Designer
2011-06-15 15:38 ` Vasiliy Kulikov [this message]
2011-06-16 14:26 ` Vasiliy Kulikov
2011-06-19 14:12 ` Vasiliy Kulikov
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=20110615153845.GA10715@albatros \
--to=segoon@openwall.com \
--cc=kernel-hardening@lists.openwall.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.