From: Adam Langley <agl@google.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: linux-kernel@vger.kernel.org, markus@google.com
Subject: Re: [RFC 1/1] seccomp: Add bitmask of allowed system calls.
Date: Fri, 15 May 2009 13:29:15 -0700 [thread overview]
Message-ID: <a84d7bc60905151329h677e5a96l76a9a7d708bfc5ad@mail.gmail.com> (raw)
In-Reply-To: <20090515195644.GA1377@ucw.cz>
On Fri, May 15, 2009 at 12:56 PM, Pavel Machek <pavel@ucw.cz> wrote:
> If you allow setuid exec here, you have added a security hole. Deny
> setuid() to sendmail and have fun...
Good point there. If you have any seccomp enabled you shouldn't be
able to run suid binaries. Being able to deny random syscalls to suid
binaries is too scary.
If this patch ever goes anywhere I'll add that.
Thanks
AGL
prev parent reply other threads:[~2009-05-15 20:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-07 21:48 Adam Langley
2009-05-07 22:14 ` Ingo Molnar
2009-05-07 22:34 ` Adam Langley
2009-05-07 23:00 ` Frederic Weisbecker
2009-05-08 5:32 ` Tom Zanussi
2009-05-08 9:19 ` Ingo Molnar
2009-05-08 11:12 ` Frederic Weisbecker
2009-05-08 9:20 ` Ingo Molnar
2009-05-08 2:37 ` James Morris
2009-05-08 9:44 ` Ingo Molnar
2009-05-15 19:56 ` Pavel Machek
2009-05-15 20:29 ` Adam Langley [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=a84d7bc60905151329h677e5a96l76a9a7d708bfc5ad@mail.gmail.com \
--to=agl@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markus@google.com \
--cc=pavel@ucw.cz \
/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®