From: "Kovacsics Róbert" <kovirobi@gmail.com>
To: Guile User Mailing List <guile-user@gnu.org>
Subject: Guile Sandbox and importing modules
Date: Tue, 7 Apr 2020 19:44:47 +0100 [thread overview]
Message-ID: <CABPkNKkW-L4shqPNrkUrVdpUs_YfxzYGcjHih5_R3WD733DLaw@mail.gmail.com> (raw)
Hi,
I have been playing around with libfive-{guile,studio}, which seems
nice so far, but one of the problems is it doesn't support importing
other modules due to the sandboxing, AFAICS
(https://github.com/libfive/libfive/issues/285). I wonder if I could
have some opinions on it, e.g. if I were to put use-modules into a
sandbox would it break the sandbox completely? Presumably if I am
importing/compiling code (such as read/eval) within the sandbox just
as if it were written inline, it won't break the sandbox -- just fail
to load. Do I have to write my own load function that does this? Will
this strategy break with compiled .go files, which might I presume
call out to arbitrary C or somesuch, and would first need to be
analysed.
Thanks,
Robert
reply other threads:[~2020-04-07 18:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CABPkNKkW-L4shqPNrkUrVdpUs_YfxzYGcjHih5_R3WD733DLaw@mail.gmail.com \
--to=kovirobi@gmail.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).