> MMM, the Ocaml-based web browser, still exists, see
> http://caml.inria.fr/archives/200005/msg00082.html.  However, last I knew,
> the Ocaml bytecode lacks the security guarantees of Java bytecode.  Dynamic
> linking will not violate stated interface constraints, but these can be
> spoofed, I believe.  

I'd be interested to know how you'd spoof them.  (Except by breaking
the MD5 crypto hash function, of course, but if you manage to do so,
that would be quite an achievement!  Not only would you immediately
get a PhD in crpytography, but you would also have a "fun" time with
men in black from various organizations...)

As far as we know, the interface checking for MMM applets is safe, but
it is very brittle: the slightest change in the browser's APIs will
cause interface checking to fail, requiring a recompile of the
applets.  That, and the need for a centralized trusted compiling
authority, makes the scheme much less practical than Java-style
bytecode verification.

- Xavier Leroy