From: Vasiliy Kulikov <segoon@openwall.com>
To: kernel-hardening@lists.openwall.com
Subject: Re: [kernel-hardening] HARDEN_VM86
Date: Sun, 19 Jun 2011 18:12:32 +0400 [thread overview]
Message-ID: <20110619141232.GA3444@albatros> (raw)
In-Reply-To: <20110615143844.GB32753@openwall.com>
Solar,
On Wed, Jun 15, 2011 at 18:38 +0400, Solar Designer wrote:
> BTW, a related syscall is modify_ldt(2). You could want to research
> what programs use it, and consider restricting it as well. Perhaps with
> a separate sysctl?
It starts to look like seccomp v2.
http://thread.gmane.org/gmane.linux.kernel/833539/focus=833864
- but with capable(CAP_SYS_RAWIO) instead of just deny and static
syscalls list. Will Drewry is trying to push his limiting patch with
ftrace-like syntax restrictions, but (a) it is not yet applied and (b)
it is not inherited by execve's:
https://lkml.org/lkml/2011/6/12/184
If it was not limited to one task it would serve our needs :(
--
Vasiliy
prev parent reply other threads:[~2011-06-19 14:12 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
2011-06-16 14:26 ` Vasiliy Kulikov
2011-06-19 14:12 ` Vasiliy Kulikov [this message]
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=20110619141232.GA3444@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox