From: "Noneayour Business" <pacificsymphony8@gmx.com>
To: guile-user@gnu.org
Subject: Re: sandboxing Guile extensions
Date: Fri, 22 Feb 2019 22:46:01 +0100 [thread overview]
Message-ID: <trinity-266d988f-710e-4e36-b4c9-00c7be1f6920-1550871961481@3c-app-mailcom-bs04> (raw)
Thanks for the help with this! I hadn't understood the docs well enough
to understand that the
sandbox module did allow restrictions on what library functions were
available.
Unfortunately the sandbox module is only available with guile 2.2+,
which makes it impractical
for my application, since I can't expect users to compile the latest
version from source.
next reply other threads:[~2019-02-22 21:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-22 21:46 Noneayour Business [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-02-15 20:31 sandboxing Guile extensions tantalum
2019-02-10 21:06 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-266d988f-710e-4e36-b4c9-00c7be1f6920-1550871961481@3c-app-mailcom-bs04 \
--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).