On 6/29/2014 1:12 AM, Brad Roberts via Digitalmars-d wrote:
A safe rule of thumb with crypto code / libraries: If the thought of writing
that type of code doesn't scare you for at least a dozen or so reasons, you
don't know enough to tread in that playground. Or you're one of the damned few
people on the planet qualified and are already working on one.
In a way, it's a bit like writing FP math functions. If using a college calculus
book as an implementation guide, the results will be algorithmically correct but
quite wrong, as FP doesn't behave like math. Getting them right is something
that PhD's in comp sci do.
Crypto takes that and squares the difficulty.
If someone wants to learn about crypto by writing crypto libraries in D, I'm all
for it.
But I'm not willing to make those part of the official D repository, with its
implicit endorsement that people could rely on them for critical applications
such as, say, banking transactions.
What we can do is simply provide a D interface to existing, vetted C crypto
libraries. The Deimos project is a fine place for those.
