From: Joris van der Hoeven <TeXmacs@math.u-psud.fr>
Cc: vdhoeven@texmcs.org
Subject: Secure evaluation
Date: Mon, 14 Jul 2003 11:36:28 +0200 (CEST) [thread overview]
Message-ID: <Pine.GSO.4.33.0307141131320.10446-100000@sunanh> (raw)
Hi,
I would like to use Guile Scheme for scripts inside documents,
a bit like Javascript in Html. Does there exist any mechanism which
forbids the use of dangerous instructions like (system "rm -rf /")
or maybe even instructions which may lead to infinite loops?
Thanks, Joris
-----------------------------------------------------------
Joris van der Hoeven <vdhoeven@texmacs.org>
http://www.texmacs.org: GNU TeXmacs scientific text editor
http://www.math.u-psud.fr/~vdhoeven: personal homepage
-----------------------------------------------------------
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
next reply other threads:[~2003-07-14 9:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-14 9:36 Joris van der Hoeven [this message]
2003-07-14 15:34 ` Secure evaluation David Allouche
2003-07-14 15:43 ` Paul Jarc
2003-07-15 8:01 ` David Allouche
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=Pine.GSO.4.33.0307141131320.10446-100000@sunanh \
--to=texmacs@math.u-psud.fr \
--cc=vdhoeven@texmcs.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).