From: Ingo Molnar <mingo@elte.hu>
To: Maciej Zenczykowski <maze@cela.pl>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Syscall security
Date: Fri, 26 Sep 2003 16:10:56 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.56.0309261609160.20113@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.44.0309261553180.6080-100000@gaia.cela.pl>
On Fri, 26 Sep 2003, Maciej Zenczykowski wrote:
> The reason I'm asking is because I want to run totally untrusted
> statically linked binary code (automatically compiled from user
> submitted untrusted sources) which only needs read/write access to stdio
> which means it only requires syscalls read/write/exit + a few more for
> memory alloc/free (like brk) + a few more generated before main is
> called (execve and uname I believe).
if this syscall activity is so low then it might be much more flexible to
control the binary via ptrace and reject all but the desired syscalls.
This will cause a context switch but if it's stdio only then it's not a
big issue. Plus this would work on any existing Linux kernel.
Ingo
next prev parent reply other threads:[~2003-09-26 14:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-26 14:05 Syscall security Maciej Zenczykowski
2003-09-26 14:10 ` Ingo Molnar [this message]
2003-09-26 14:16 ` Maciej Zenczykowski
2003-09-26 14:19 ` Ingo Molnar
2003-09-26 14:21 ` Ruth Ivimey-Cook
2003-09-26 16:14 ` Maciej Zenczykowski
2003-09-26 15:01 ` Davide Libenzi
2003-09-26 16:18 ` Maciej Zenczykowski
2003-09-28 11:38 ` Kenneth Johansson
2003-09-26 15:16 ` Muli Ben-Yehuda
2003-09-26 16:25 ` Maciej Zenczykowski
2003-09-26 15:18 ` Joe McClain
2003-09-26 16:10 ` Chris Wright
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=Pine.LNX.4.56.0309261609160.20113@localhost.localdomain \
--to=mingo@elte.hu \
--cc=linux-kernel@vger.kernel.org \
--cc=maze@cela.pl \
/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;
as well as URLs for NNTP newsgroup(s).