Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: "Nicolas Cannasse" <warplayer@free.fr>
To: "Richard Jones" <rich@annexia.org>, <caml-list@inria.fr>
Subject: Re: [Caml-list] Securely loading and running untrusted modules
Date: Tue, 5 Apr 2005 21:55:32 +0900	[thread overview]
Message-ID: <000f01c539de$c1859fd0$0c05a8c0@PWARP> (raw)
In-Reply-To: <20050405121459.GA29378@furbychan.cocan.org>

> To prevent infinite loops, starting an alarm(2) before loading the
> module should kill the Apache process if it uses too much CPU time.
>
> I'm fairly sure that the method above should cope with everything
> barring bugs in the compiler and bugs in SafeAPI.
>
> Am I thinking right?
>
> Rich.

I think that current VM is optimized for speed and doesn't do more bytecode
checking than strictly necessary. That means that someone could forge some
bytecode file that would take control of the VM and then can call the whole
C api. Tricky, but feasible.
You might need to add load-time or runtime bytecode checks in order to
secure the VM.

Regards,
Nicolas Cannasse


  reply	other threads:[~2005-04-05 12:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-05 12:14 Richard Jones
2005-04-05 12:55 ` Nicolas Cannasse [this message]
2005-04-05 13:16   ` [Caml-list] " Richard Jones
2005-04-05 14:09     ` Alex Baretta
     [not found]     ` <42529C01.2080609@barettadeit.com>
2005-04-05 14:17       ` Richard Jones
2005-04-05 14:36         ` Jacques Garrigue
2005-04-05 20:58           ` sejourne_kevin
2005-04-05 21:02             ` Jacques Garrigue
2005-04-06  7:59               ` sejourne_kevin
2005-04-05 14:38         ` Virgile Prevosto
2005-04-05 14:40         ` Daniel Bünzli

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='000f01c539de$c1859fd0$0c05a8c0@PWARP' \
    --to=warplayer@free.fr \
    --cc=caml-list@inria.fr \
    --cc=rich@annexia.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