diff options
author | Jeffrey Walton <noloader@gmail.com> | 2017-04-24 05:05:14 -0400 |
---|---|---|
committer | Jeffrey Walton <noloader@gmail.com> | 2017-04-24 05:05:14 -0400 |
commit | 2297dd000a7cf2831095ba59be2ed653ea3bd884 (patch) | |
tree | 7aa629b92a168f33e8bc390de698a09c7286144f /esign.cpp | |
parent | 64f1b50b7fc5cf887becd70b3e35ded6d98bf639 (diff) | |
download | cryptopp-git-2297dd000a7cf2831095ba59be2ed653ea3bd884.tar.gz |
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.
Diffstat (limited to 'esign.cpp')
-rw-r--r-- | esign.cpp | 14 |
1 files changed, 7 insertions, 7 deletions
@@ -21,15 +21,15 @@ NAMESPACE_BEGIN(CryptoPP) #if defined(CRYPTOPP_DEBUG) && !defined(CRYPTOPP_DOXYGEN_PROCESSING)
void ESIGN_TestInstantiations()
{
- ESIGN<SHA>::Verifier x1(1, 1);
- ESIGN<SHA>::Signer x2(NullRNG(), 1);
- ESIGN<SHA>::Verifier x3(x2);
- ESIGN<SHA>::Verifier x4(x2.GetKey());
- ESIGN<SHA>::Verifier x5(x3);
- ESIGN<SHA>::Signer x6 = x2;
+ ESIGN<SHA1>::Verifier x1(1, 1);
+ ESIGN<SHA1>::Signer x2(NullRNG(), 1);
+ ESIGN<SHA1>::Verifier x3(x2);
+ ESIGN<SHA1>::Verifier x4(x2.GetKey());
+ ESIGN<SHA1>::Verifier x5(x3);
+ ESIGN<SHA1>::Signer x6 = x2;
x6 = x2;
- x3 = ESIGN<SHA>::Verifier(x2);
+ x3 = ESIGN<SHA1>::Verifier(x2);
x4 = x2.GetKey();
}
#endif
|