Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Thorsten Ohl <ohl@hep.tu-darmstadt.de>
To: caml-list@inria.fr
Cc: Markus Mottl <mottl@miss.wu-wien.ac.at>
Cc: Vitaly Lugovsky <vsl@ontil.ihep.su>
Subject: Re: Signatures (was: Reverse-Engineering Bytecode)
Date: Tue, 13 Jun 2000 14:54:58 +0200 (CEST)	[thread overview]
Message-ID: <14662.12066.90625.170479@heplix4.ikp.physik.tu-darmstadt.de> (raw)
In-Reply-To: <20000612162319.A3314@miss.wu-wien.ac.at>

> Even better would be a fixed point condition that would allow to
> print a warning message: ``The sources have been modified, you can
> do anything you want, but don't blame me or the results.''

Vitaly Lugovsky wrote:

> But it don't need a core support from OCaml - you just can use MD5
> checksum or something like this....

I'm not so sure.  I woudl liek to access a checksum of the actual
sources that have been used to compile the module implementations in
the currently running program, just like Dynlink does for module
types.

One can play games with MD5 and a `Signatures' module in the Makefile,
but this is not 100%ly secure, because the code could be compiled by
hand, without updating the checksums.

Or am I missing something here?

Cheers,
-Thorsten
-- 
Thorsten Ohl, Physics Department, TU Darmstadt -- ohl@hep.tu-darmstadt.de
http://heplix.ikp.physik.tu-darmstadt.de/~ohl/ [<=== PGP public key here]




  reply	other threads:[~2000-06-13 16:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-06-07 21:41 Reverse-Engineering Bytecode: A Possible Commercial Objection To O'Caml Michael Donat
2000-06-09 17:17 ` Signatures (was: Reverse-Engineering Bytecode) Thorsten Ohl
2000-06-09 21:56   ` Vitaly Lugovsky
2000-06-12 14:23     ` Markus Mottl
2000-06-13 12:54       ` Thorsten Ohl [this message]
2000-06-13 13:02         ` Vitaly Lugovsky

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=14662.12066.90625.170479@heplix4.ikp.physik.tu-darmstadt.de \
    --to=ohl@hep.tu-darmstadt.de \
    --cc=caml-list@inria.fr \
    --cc=mottl@miss.wu-wien.ac.at \
    /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