From: Xavier Leroy <xavier.leroy@inria.fr>
To: "Yurii A. Rashkovskii" <yrashk@openeas.org>
Cc: Ohad Rodeh <ORODEH@il.ibm.com>, caml-list@inria.fr
Subject: Re: [Caml-list] OcamlSpread 0.0.1 released
Date: Fri, 20 Sep 2002 15:15:11 +0200 [thread overview]
Message-ID: <20020920151510.A19108@pauillac.inria.fr> (raw)
In-Reply-To: <14331741431.20020918205930@openeas.org>; from yrashk@openeas.org on Wed, Sep 18, 2002 at 08:59:30PM +0300
> The question is not a speed, but strength of the algorithms. I think
> that Ensemble *should* have storng algorithms for security or
> pluggable interface to switch in OpenSSL, cryptokit or whatsoever.
As Ohad said, OpenSSL offers more ciphers than my Cryptokit, and some
of them probably run faster in OpenSSL, but still the ciphers and
hashes supported by Cryptokit are entirely standard (AES, Triple DES,
RC4, RSA, etc) and have no known cryptographic weaknesses -- provided
adequate key sizes are selected, of course.
Security holes are much more likely to arise as a consequence of
incorrect use of these algorithms, e.g. at the cryptographic protocol
level, than as a consequence of a weakness of the algorithms
themselves.
- Xavier Leroy
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next prev parent reply other threads:[~2002-09-20 13:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2002-09-20 14:45 ` Arnaud SAHUGUET
-- strict thread matches above, loose matches on Subject: below --
2002-09-20 16:14 MONIN Jean-Francois FTRD/DTL/LAN
2002-09-20 18:57 ` Arnaud SAHUGUET
2002-09-18 20:49 Re[6]: " Ohad Rodeh
2002-09-18 22:44 ` Blair Zajac
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=20020920151510.A19108@pauillac.inria.fr \
--to=xavier.leroy@inria.fr \
--cc=ORODEH@il.ibm.com \
--cc=caml-list@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