From: Marius Vollmer <mvo@zagadka.de>
Cc: guile-user@gnu.org
Subject: Re: Refactoring dynamic roots
Date: Sat, 29 Jan 2005 01:17:52 +0100 [thread overview]
Message-ID: <87vf9hjdfz.fsf@zagadka.de> (raw)
In-Reply-To: <87acqtfeod.fsf@zip.com.au> (Kevin Ryde's message of "Sat, 29 Jan 2005 08:04:50 +1100")
Kevin Ryde <user42@zip.com.au> writes:
> Marius Vollmer <marius.vollmer@uni-dortmund.de> writes:
>>
>> The other thing that dynamic roots do is to isolate changes to the
>> dynamic state. For example, calls to set-current-output-port or
>> fluid-set! have no effects outside of a dynamic root. This might be
>> useful when running arbitrary code since the caller can protect itself
>> from unexpected changes to the dynamic state. (This is not _that_
>> useful for sandboxing code since the code can of course change the
>> global state of Guile arbitrarily unless other measures are taken.)
>
> I'm unsure about this bit. If you trust the code enough not to mangle
> global variables, can't you trust it enough not to mangle fluids too?
Hmm, it is probably not so much about trust, but about being nice to
the code that you run: you want to give it its own dynamic state
because that is very useful.
Of course you have to trust the code that you run. If you do not
trust it but want to run it anyway, my answer would be to isolate the
whole guile process with the means provided by the OS, such as
chrooting it, running it as nobody, etc.
--
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3 331E FAF8 226A D5D4 E405
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2005-01-29 0:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-24 20:55 Refactoring dynamic roots Marius Vollmer
2005-01-25 10:03 ` Andy Wingo
2005-01-28 21:03 ` Kevin Ryde
2005-01-29 0:13 ` Marius Vollmer
2005-01-29 17:10 ` Neil Jerram
2005-02-01 16:20 ` Marius Vollmer
2005-02-02 5:56 ` Neil Jerram
2005-02-01 16:23 ` Marius Vollmer
2005-01-28 21:04 ` Kevin Ryde
2005-01-29 0:17 ` Marius Vollmer [this message]
2005-02-01 23:43 ` Kevin Ryde
2005-02-02 13:55 ` Marius Vollmer
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=87vf9hjdfz.fsf@zagadka.de \
--to=mvo@zagadka.de \
--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).