I accidentally enable the CRYPTOPP_MAINTAIN_BACKWARDS_COMPATIBILITY define
today. It resulted in:
g++ -DNDEBUG -g2 -O3 -fPIC -fsanitize=undefined -march=native -pipe -c
dsa.cpp
In file included from dsa.cpp:7:0:
dsa.h:24:34: error: ‘MIN_PRIME_LENGTH’ is not a member of ‘CryptoPP::DSA
{aka CryptoPP::DSA2<CryptoPP::SHA1>}’
const int MIN_DSA_PRIME_LENGTH = DSA::MIN_PRIME_LENGTH;
^
dsa.h:25:34: error: ‘MAX_PRIME_LENGTH’ is not a member of ‘CryptoPP::DSA
{aka CryptoPP::DSA2<CryptoPP::SHA1>}’
const int MAX_DSA_PRIME_LENGTH = DSA::MAX_PRIME_LENGTH;
...
We can take the time to fix it. But moving forward, I envision we will have
a new generation of things to protect with
CRYPTOPP_MAINTAIN_BACKWARDS_COMPATIBILITY.
Because we are going to use CRYPTOPP_MAINTAIN_BACKWARDS_COMPATIBILITY for
things like compatibility when SHA-1 and friends move into the Weak
namespace, I'd like to begin purging current generation items.
To be clear, this is not an actionable item for me. I won't stop what I am
doing and perform a purge. But I want to make sure we are clear on moving
forward when the next generation of items gets protected by it.
Does anyone have any thoughts, comments or objections?
--
--
You received this message because you are subscribed to the "Crypto++ Users"
Google Group.
To unsubscribe, send an email to [email protected].
More information about Crypto++ and this group is available at
http://www.cryptopp.com.
---
You received this message because you are subscribed to the Google Groups
"Crypto++ Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
