On Sun, 29 Jun 2014 05:33:06 -0700, Etienne <[email protected]> wrote:
On 2014-06-29 3:19 AM, Adam Wilson wrote:
Botan isn't as battle-tested as OpenSSL or Crypto++ but it was designed
from the ground up to mitigate or prevent the kind of problems that
OpenSSL is currently experiencing, and was implemented by someone who
has done multiple Cryptographic Module Verifications for NIST. I
personally went with Botan because it's relatively easy to create
bindings for the languages I use and API is relatively sane for a crypto
library (I'm looking at you OpenSSL).
It also seems to link statically with D projects, although it requires
MSVC. I'd certainly build a dub package for it, but I'm too busy paving
the way towards a native TLS library although I intend on using your
crypto interface with it. ;)
The static linking is due to the fact that D's shared library support is
very uneven across platforms. The .NET binding is fully modularized and
will load the correct Arch at runtime to support the AnyCPU arch.
--
Adam Wilson
GitHub/IRC: LightBender
Aurora Project Coordinator
