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/default.h b/default.h
index 78bc0d19..691cbbb3 100644
--- a/default.h
+++ b/default.h
@@ -19,7 +19,7 @@ NAMESPACE_BEGIN(CryptoPP)
 //! \brief Legacy block cipher for LegacyEncryptor, LegacyDecryptor, LegacyEncryptorWithMAC and LegacyDecryptorWithMAC

 typedef DES_EDE2 LegacyBlockCipher;

 //! \brief Legacy hash for use with LegacyEncryptorWithMAC and LegacyDecryptorWithMAC

-typedef SHA LegacyHashModule;

+typedef SHA1 LegacyHashModule;

 //! \brief Legacy HMAC for use withLegacyEncryptorWithMAC and LegacyDecryptorWithMAC

 typedef HMAC<LegacyHashModule> LegacyMAC;