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 /sha.h | |
| 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 'sha.h')
| -rw-r--r-- | sha.h | 2 |
1 files changed, 0 insertions, 2 deletions
@@ -30,8 +30,6 @@ public: CRYPTOPP_STATIC_CONSTEXPR const char* CRYPTOPP_API StaticAlgorithmName() {return "SHA-1";}
};
-typedef SHA1 SHA; // for backwards compatibility
-
//! \class SHA256
//! \brief SHA-256 message digest
//! \sa <a href="http://www.weidai.com/scan-mirror/md.html#SHA-256">SHA-256</a>
|