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 /gfpcrypt.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 'gfpcrypt.cpp')
| -rw-r--r-- | gfpcrypt.cpp | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/gfpcrypt.cpp b/gfpcrypt.cpp index 9e821c91..6494b084 100644 --- a/gfpcrypt.cpp +++ b/gfpcrypt.cpp @@ -23,12 +23,12 @@ NAMESPACE_BEGIN(CryptoPP) #if defined(CRYPTOPP_DEBUG) && !defined(CRYPTOPP_DOXYGEN_PROCESSING)
void TestInstantiations_gfpcrypt()
{
- GDSA<SHA>::Signer test;
- GDSA<SHA>::Verifier test1;
+ GDSA<SHA1>::Signer test;
+ GDSA<SHA1>::Verifier test1;
DSA::Signer test5(NullRNG(), 100);
DSA::Signer test2(test5);
- NR<SHA>::Signer test3;
- NR<SHA>::Verifier test4;
+ NR<SHA1>::Signer test3;
+ NR<SHA1>::Verifier test4;
DLIES<>::Encryptor test6;
DLIES<>::Decryptor test7;
}
|