From: Xavier Leroy <Xavier.Leroy@inria.fr>
To: Michael Hicks <mwh@dsl.cis.upenn.edu>
Cc: caml-list@inria.fr
Subject: Re: dynamic loading of Caml bytecode
Date: Thu, 11 Nov 1999 22:01:24 +0100 [thread overview]
Message-ID: <19991111220124.07336@pauillac.inria.fr> (raw)
In-Reply-To: <199911081607.LAA27012@codex.cis.upenn.edu>; from Michael Hicks on Mon, Nov 08, 1999 at 11:07:23AM -0500
> I wonder if anyone could elaborate for me on the safety of dynamically
> loaded Ocaml bytecode? Is it possible to load bytecode that is not
> well-formed or type-correct (thus resulting in a core-dump or other
> misbehavior at runtime)? I understand that interfaces are checked for
> consistency using MD5 hashes, but I'm curious about the internal consistency
> of the bytecode file itself.
Essentially no consistency checks are performed by the dynamic loader.
Just like the MD5-based interface consistency mechanism that you
mention, the whole dynamic loader assumes that its input has been
produced by a correct OCaml compiler and not modified since. That's
why in the MMM design we had to rely on cryptographic signatures to
ensure the well-formedness of applet code.
- Xavier Leroy
prev parent reply other threads:[~1999-11-12 9:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-08 16:07 Michael Hicks
1999-11-11 21:01 ` Xavier Leroy [this message]
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=19991111220124.07336@pauillac.inria.fr \
--to=xavier.leroy@inria.fr \
--cc=caml-list@inria.fr \
--cc=mwh@dsl.cis.upenn.edu \
/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 NNTP newsgroup(s).