Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: "MONIN Jean-Francois FTRD/DTL/LAN" <jeanfrancois.monin@rd.francetelecom.com>
To: "Arnaud SAHUGUET" <sahuguet@lucent.com>
Cc: "Xavier Leroy" <xavier.leroy@inria.fr>,
	"Yurii A. Rashkovskii" <yrashk@openeas.org>,
	"Ohad Rodeh" <ORODEH@il.ibm.com>, <caml-list@inria.fr>
Subject: Re: [Caml-list] OcamlSpread 0.0.1 released
Date: Fri, 20 Sep 2002 18:14:04 +0200	[thread overview]
Message-ID: <15755.18764.944202.516163@localhost.localdomain> (raw)

[-- Attachment #1: Type: text/plain, Size: 1178 bytes --]

On a first reading I tended to agree with some
of your arguments. However:

> When choosing a crypto package, there are a few points to consider:
> [...]
> - the maintenance of the package
> Flaws are being discovered everyday. It is better to use a crypto
package
> which is widely used, tested and maintained.
> [...]
> I think the last and worst thing to do is to re-implement some crypto
from
> scratch.

But what do you think of:

"When choosing an operating system, there are a few points to consider:
[...]
- the maintenance of the OS
Flaws are being discovered everyday. It is better to use an OS
which is widely used, tested and maintained.
[...]
I think the last and worst thing to do is to re-implement some OS from
scratch."

More seriously, perhaps, a well-known source of flaws is complexity.
Expressing algorithms in Ocaml is often (much) less complex than 
in C...

I cannot be more specific in this case, because I did not examine
the implementations. However, as you say yourself:

> When choosing a crypto package, there are a few points to consider:
> 
> - the people who implement the package

Regards,
  Jean-Francois

[-- Attachment #2: Type: text/html, Size: 2354 bytes --]

             reply	other threads:[~2002-09-23  4:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-20 16:14 MONIN Jean-Francois FTRD/DTL/LAN [this message]
2002-09-20 16:18 ` Re[2]: " Yurii A. Rashkovskii
2002-09-20 18:57 ` Arnaud SAHUGUET
  -- strict thread matches above, loose matches on Subject: below --
2002-09-18 20:49 Re[6]: " Ohad Rodeh
2002-09-18 22:44 ` Blair Zajac
2002-09-18 16:56 Re[4]: " Ohad Rodeh
2002-09-18 17:59 ` Re[6]: " Yurii A. Rashkovskii
2002-09-20 13:15   ` Xavier Leroy
2002-09-20 14:45     ` Arnaud SAHUGUET
2002-09-17 20:06 Ohad Rodeh
2002-09-17 11:15 Yurii A. Rashkovskii

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=15755.18764.944202.516163@localhost.localdomain \
    --to=jeanfrancois.monin@rd.francetelecom.com \
    --cc=ORODEH@il.ibm.com \
    --cc=caml-list@inria.fr \
    --cc=sahuguet@lucent.com \
    --cc=xavier.leroy@inria.fr \
    --cc=yrashk@openeas.org \
    /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