From: "Noneayour Business" <pacificsymphony8@gmx.com>
To: guile-user@gnu.org
Subject: sandboxing Guile extensions
Date: Sun, 10 Feb 2019 22:06:12 +0100 [thread overview]
Message-ID: <trinity-e84838dd-4b91-4f88-9c95-4d391ccbb366-1549832772713@3c-app-mailcom-bs07> (raw)
I have a GUI app
http://www.lightandmatter.com/ogr/ogr.html
in which I've just implemented a very rudimentary extension mechanism
using Guile. I'm not an experienced lisp programmer at all. This has
been
my first use of lisp beyond "hello, world."
The purpose of my extension is to let users run their own arbitrary
code
in certain situations. However, this means that someone could in
principle
create a Trojan horse attack in which they embed some malicious Guile
code in a document and send it to someone else and try to get them to
open the document.
I see that Guile 2.2.1 has a sandboxing mechanism:
https://www.gnu.org/software/guile/manual/html_node/Sandboxed-Evaluatio
n.html
However, this seems entirely focused on preventing excessive use of
resources. Is there any way to have Guile run in a sandbox similar to
the javascript or java applet sandbox, where it doesn't have access to
the file system and so on? E.g., could I delete certain parts of the
libraries
before handing control over to the user-supplied code, or can the
interpreter
be started up without some of the standard libraries?
I'm currently running Guile by starting up an interpreter through a
shell
for each evaluation of the user's function:
https://github.com/bcrowell/opengrade/blob/master/Extension.pm
Thanks in advance for any suggestions!
Ben Crowell
next reply other threads:[~2019-02-10 21:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-10 21:06 Noneayour Business [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-02-15 20:31 sandboxing Guile extensions tantalum
2019-02-22 21:46 Noneayour Business
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=trinity-e84838dd-4b91-4f88-9c95-4d391ccbb366-1549832772713@3c-app-mailcom-bs07 \
--to=pacificsymphony8@gmx.com \
--cc=guile-user@gnu.org \
/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).