[bind10-dev] [svn] commit: r1108 - in /branches/each-nsec3/src/lib/dns/cpp: Makefile.am base32.cc base32.h sha1.cc sha1.h tests/Makefile.am tests/base32_unittest.cc tests/sha1_unittest.cc

[Evan Hunt]

> Did you consider using the author's C++ version? His website indicates 
> he had fixes and improvements since his old RFC implementation.

I considered several things, and chose the path that seemed most likely
to get the problem out of my way quickly.

In the long term, I would favor using crypto++, which includes SHA1 and
every other crypto algorithm we'll be needing, plus encoders and decoders
for base32, base64 and hex.

In the meantime I honestly don't care what we use, as long as it produces
the right hash according to the standard.  This code obviously does so (it
literally *is* the standard), so I need to move on and work on NSEC3.  We
can swap in a different SHA1 implementation later.

                                                eh