[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date: Sat, 29 Sep 2012 20:12:15 +0400
From: Alexander Cherepanov <cherepan@...me.ru>
To: john-dev@...ts.openwall.com
Subject: Re: 1.7.9-jumbo-7
On 2012-09-19 20:41, jfoug wrote:
> This brings up a 'good' issue to discuss. In many places we are using oSSL
> default #define constants. We probably should NOT do this, since we may not
> be running under oSSL. We have taken it to the point, where we 'emulate'
> and define the same constants on some non oSSL builds, to use the same name
> as the oSSL.
>
> What I believe we 'should' do is to have our OWN set of constants. Then if
> under oSSL build, we set out constants to use the oSSL. If building under
> OSX, we use theirs. If under wysiwyg-crypt, we theirs, etc. If our own, we
> simply set them appropriately.
Yeah, it would be cool to be able to switch crypto libraries or even to
be able to take each crypto function from the library where it's the
fastest (if several libraries are available) and to replace functions
with our own. And do it without changing format files.
Now we see that it could also be useful because of copyright issues.
There are some general crypto library comparisons:
https://en.wikipedia.org/wiki/Comparison_of_TLS_Implementations
http://curl.haxx.se/docs/ssl-compared.html
old speed comparison:
http://idlebox.net/2008/0714-cryptography-speedtest-comparison/
but there is plenty of material here:
http://bench.cr.yp.to/
with source code available here:
http://hyperelliptic.org/ebats/supercop-20120918.tar.bz2
Not everything free in there but there are some public domain etc.
implementations
--
Alexander Cherepanov
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
