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 /luc.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 'luc.h')
| -rw-r--r-- | luc.h | 8 |
1 files changed, 4 insertions, 4 deletions
@@ -152,11 +152,11 @@ struct LUCSS : public TF_SS<LUC, STANDARD, H> };
// analogous to the RSA schemes defined in PKCS #1 v2.0
-typedef LUCES<OAEP<SHA> >::Decryptor LUCES_OAEP_SHA_Decryptor;
-typedef LUCES<OAEP<SHA> >::Encryptor LUCES_OAEP_SHA_Encryptor;
+typedef LUCES<OAEP<SHA1> >::Decryptor LUCES_OAEP_SHA_Decryptor;
+typedef LUCES<OAEP<SHA1> >::Encryptor LUCES_OAEP_SHA_Encryptor;
-typedef LUCSS<PKCS1v15, SHA>::Signer LUCSSA_PKCS1v15_SHA_Signer;
-typedef LUCSS<PKCS1v15, SHA>::Verifier LUCSSA_PKCS1v15_SHA_Verifier;
+typedef LUCSS<PKCS1v15, SHA1>::Signer LUCSSA_PKCS1v15_SHA_Signer;
+typedef LUCSS<PKCS1v15, SHA1>::Verifier LUCSSA_PKCS1v15_SHA_Verifier;
// ********************************************************
|