unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: "Thompson, David" <dthompson2@worcester.edu>
To: Matthew Keeter <matt.j.keeter@gmail.com>
Cc: Guile User <guile-user@gnu.org>
Subject: Re: Embedding Guile with sandboxing
Date: Sat, 21 Nov 2015 16:40:11 -0500	[thread overview]
Message-ID: <CAJ=RwfYL+JMYvv8kpqWQUhLRTzNFV4A7uQprNOQ=g+vj2D6JSw@mail.gmail.com> (raw)
In-Reply-To: <1E9F5137-A070-4E3B-A781-FBAE80810FE6@gmail.com>

On Sat, Nov 21, 2015 at 1:35 PM, Matthew Keeter <matt.j.keeter@gmail.com> wrote:
> I’m currently embedding Python in a C / C++ application that evaluates user-provided scripts.
>
> Obviously, this is terribly unsafe: user-provided scripts can execute arbitrary malicious actions,
> and there’s no good way to sandbox Python in a desktop context.
>
> If I were to replace Python with Guile, is there a way to sandbox it so that arbitrary (perhaps
> malicious) user-provided scripts can be run safely?

I recommend using the features of the underlying operating system to
provide the sandbox.  In Linux, one can create new
user/pid/network/mount/etc. namespaces (in other words, a "container")
that isolate a process (or processes) from the rest of the system.
Additionally, you should run the program as an unprivileged user
inside of a chroot.

- Dave



  parent reply	other threads:[~2015-11-21 21:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-21 18:35 Embedding Guile with sandboxing Matthew Keeter
2015-11-21 21:39 ` Pascal J. Bourguignon
2015-11-24 16:35   ` Amirouche Boubekki
2015-11-21 21:40 ` Thompson, David [this message]
2015-11-22 10:06 ` Arne Babenhauserheide
2015-11-25 11:07   ` tomas
2015-11-22 15:51 ` Christopher Allan Webber
2015-11-23  0:50   ` Roberto Baleno
2015-11-23 14:55     ` Matthew Keeter
2015-11-25 14:36       ` Christopher Allan Webber

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

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAJ=RwfYL+JMYvv8kpqWQUhLRTzNFV4A7uQprNOQ=g+vj2D6JSw@mail.gmail.com' \
    --to=dthompson2@worcester.edu \
    --cc=guile-user@gnu.org \
    --cc=matt.j.keeter@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).