From: "Michael Donat" <donat@intergate.bc.ca>
To: <caml-list@inria.fr>
Subject: Re: Reverse-Engineering Bytecode: A Possible Commercial Objection To O'Caml
Date: Wed, 7 Jun 2000 14:41:27 -0700 [thread overview]
Message-ID: <003a01bfd0c9$9f1d1370$67adc2cf@machiavelli> (raw)
>How can companies protect their bytecode, at least their modules, from
reverse
>engineering?
I believe that if someone has the desire to reverse engineer OCaml bytecode
someone will also have these other capabilities:
1) Be able to reverse engineer native code.
2) Be able to run the OCaml bytecode system in a debugger, stop after your
bytecode was decrypted, and reverse engineer it from there.
I don't see a benefit in having an OCaml module encryption system.
If you want to encrypt important portions of your app, you might consider
producing your own bytecode system. The main benefit of this approach is
that your bytecode is private, thus dramatically intensifying the effort
required to reverse engineer. I think this would be a much more effective
use of time than implementing an OCaml module encryption system.
Michael Donat
next reply other threads:[~2000-06-08 20:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-07 21:41 Michael Donat [this message]
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
2000-06-13 13:02 ` Vitaly Lugovsky
-- strict thread matches above, loose matches on Subject: below --
2000-06-09 18:18 Reverse-Engineering Bytecode: A Possible Commercial Objection To O'Caml Brent Fulgham
2000-06-09 16:13 Brent Fulgham
2000-06-08 21:58 Brent Fulgham
2000-06-06 20:46 Daniel Ortmann
2000-06-07 20:23 ` Markus Mottl
2000-06-07 22:02 ` Max Skaller
2000-06-07 22:15 ` Max Skaller
2000-06-08 8:54 ` Sven LUTHER
2000-06-08 22:36 ` Daniel Ortmann
2000-06-09 13:34 ` Sven LUTHER
2000-06-09 22:06 ` Vitaly Lugovsky
2000-06-10 14:41 ` Gerd Stolpmann
2000-06-09 15:44 ` Julian Assange
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='003a01bfd0c9$9f1d1370$67adc2cf@machiavelli' \
--to=donat@intergate.bc.ca \
--cc=caml-list@inria.fr \
/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