Removed "typedef SHA1 SHA" (Issue 369)

This should have happened when we removed most of MAINTAIN_BACKWARDS_COMPATIBILITY artifacts. Its not practical move SHA1 into Weak:: namespace or "typedef SHA256 SHA" because SHA1 is too intertwined at the moment.

In the interim, maybe we can place SHA1 in both CryptoPP:: and Weak:: namespaces. This will allow us to transition into Weak::SHA1 over time, and signal to users SHA1 should be avoided.

1 files changed, 1 insertions, 1 deletions

diff --git a/fipsalgt.cpp b/fipsalgt.cpp
index 26ce6477..ccba9940 100644
--- a/fipsalgt.cpp
+++ b/fipsalgt.cpp
@@ -457,7 +457,7 @@ protected:
 					Integer p, q, h, g;

 					int counter;

 

-					SecByteBlock seed(SHA::DIGESTSIZE);

+					SecByteBlock seed(SHA1::DIGESTSIZE);

 					do

 					{

 						m_rng.GenerateBlock(seed, seed.size());