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/seal.cpp b/seal.cpp
index d0ba4fce..acc4e4e5 100644
--- a/seal.cpp
+++ b/seal.cpp
@@ -39,7 +39,7 @@ word32 SEAL_Gamma::Apply(word32 i)
 	{

 		memcpy(Z, H, 20);

 		D[0] = shaIndex;

-		SHA::Transform(Z, D);

+		SHA1::Transform(Z, D);

 		lastIndex = shaIndex;

 	}

 	return Z[i%5];