From: Goswin von Brederlow <goswin-v-b@web.de>
To: Dario Teixeira <darioteixeira@yahoo.com>
Cc: caml-list@inria.fr, Sylvain Le Gall <sylvain@le-gall.net>
Subject: Re: [Caml-list] Re: Cryptokit and HMAC-SHA256
Date: Thu, 22 Jul 2010 10:37:42 +0200 [thread overview]
Message-ID: <87vd87ykrt.fsf@frosties.localdomain> (raw)
In-Reply-To: <317672.81389.qm@web111509.mail.gq1.yahoo.com> (Dario Teixeira's message of "Wed, 21 Jul 2010 14:22:58 -0700 (PDT)")
Dario Teixeira <darioteixeira@yahoo.com> writes:
> Hi,
>
>> If you decide to code the solution and provide the patch, I will be
>> happy to apply it to cryptokit (if the main author of cryptokit accepts
>> it, of course).
>
> I'm attaching the patches adding support for HMAC-SHA256 and HMAC-RIPEMD160
> (I don't need the latter, but for the sake of completeness it seemed silly
> not to support it as well). Note that these are *very* straightforward
> patches -- kudos to Xavier for making Cryptokit so easy to extend.
>
> The caveat is that I'm not a cryptographer. I did, however, verify that
> these new HMACs pass all the test cases listed in RFC4231 (for HMAC-SHA256)
> and RFC2286 (for HMAC-RIPEMD160).
>
> Thanks for your attention!
> Cheers,
> Dario Teixeira
While you are patching cryptokit anyway would it be possible to also add
functions to work on Bigarrays?
One huge advantage of bigarray is that the data region is allocated
outside the GC heap and will never move. That means one can use
enter_blocking_section() / leave_blocking_section() while calculating
the checksum for a block of data. For multithreaded applications that
can speed up the program by the number of cores present.
MfG
Goswin
next prev parent reply other threads:[~2010-07-22 8:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-21 21:22 Dario Teixeira
2010-07-22 8:37 ` Goswin von Brederlow [this message]
2010-07-22 8:49 ` Sylvain Le Gall
2010-07-22 9:44 ` [Caml-list] " Dario Teixeira
2010-07-22 13:24 ` Goswin von Brederlow
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=87vd87ykrt.fsf@frosties.localdomain \
--to=goswin-v-b@web.de \
--cc=caml-list@inria.fr \
--cc=darioteixeira@yahoo.com \
--cc=sylvain@le-gall.net \
/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