caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Daniel Ortmann <ortmann@vnet.ibm.com>
To: caml-list@inria.fr
Subject: Reverse-Engineering Bytecode: A Possible Commercial Objection To O'Caml
Date: Tue, 6 Jun 2000 15:46:06 -0500	[thread overview]
Message-ID: <200006062047.QAA08876@northrelay03.pok.ibm.com> (raw)

Sirs,

With the intent of furthering the practical commercial use of O'Caml, or at
least eliminating some possible objections to its use ...  I submit the
following observations and questions for your consideration:


I have asked myself "How might companies object to Objective Caml?"

The thought occurs to me that companies may wish to:
- develop and sell byte-compiled O'Caml modules
- develop and sell applications which use dynamically loaded modules
- protect their actual source code

Because of the well-thought regularity of O'Caml bytecode, the ease of viewing
(for example) emacs elisp bytecode in emacs, and the unusual numbers of bright
people working with O'Caml ...

... it occurs to me that companies may be concerned about the ease of "reverse
engineering" their byte compiled software modules and thus object to Objective
Caml.

So.

How can companies protect their bytecode, at least their modules, from reverse
engineering?

1) The idea occurs to me that O'Caml might support various standard encryption
   modules using different types of encryption techniques (DES, PGP, etc).
2) Perhaps user encryption could also be supported.
3) Perhaps the encryption modules should be composeable, multiple modules
   being used to derive another module.
4) What about using public/private keys and key management?
5) Should this be integrated with licensing?  What licensing techniques are
   available on Windows?  Mac?  Unix?  Other?  (O'Caml WILL get big
   commercially, and WILL need to address this eventually.)
6) What things should be visible non-encrypted in cmi/cmo/other files?
7) Should such encryption be available via marshalling?  If not, might some
   needs be common?


Philosophically speaking, earning money and protecting the rewards of hard
work are not bad a priori.  There *will* be an exchange of value; that
exchange may be either with or without "concern for your fellow man".  In
fact, one way of looking at a dollar bill is as a type of "certificate of
service to your fellow man".

--
Daniel Ortmann, IBM Circuit Technology, Rochester, MN 55901-7829
ortmann@vnet.ibm.com or ortmann@us.ibm.com and 507.253.6795 (external)
ortmann@rchland.ibm.com and tieline 8.553.6795 (internal)
ortmann@isl.net and 507.288.7732 (home)

"The answers are so simple, and we all know where to look,
but it's easier just to avoid the question." -- Kansas




             reply	other threads:[~2000-06-07 18:22 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-06-06 20:46 Daniel Ortmann [this message]
2000-06-07 20:23 ` Markus Mottl
2000-06-07 22:02 ` Max Skaller
2000-06-09 12:14   ` OCaml book Joshua D. Guttman
2000-06-13 16:53     ` Julian Assange
2000-06-07 22:15 ` Reverse-Engineering Bytecode: A Possible Commercial Objection To O'Caml 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
2000-06-07 21:41 Michael Donat
2000-06-08 21:58 Brent Fulgham
2000-06-09 16:13 Brent Fulgham
2000-06-09 18:18 Brent Fulgham

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=200006062047.QAA08876@northrelay03.pok.ibm.com \
    --to=ortmann@vnet.ibm.com \
    --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;
as well as URLs for NNTP newsgroup(s).