Hi Everyone,

CVE-2016-7420 has me questioning some of the wisdom in config.recommend and 

config.recommend removes undefined behavior, but it requires user to do 
something special. I believe most users don't need the compatibility 
provided in config.h. Failure to use config.recommend is a replay of not 
defining NDEBUG for production/release builds when using other tools, like 
Autotools, CMake, Eclipse, Xcode, etc.

If RTFM was going to work, it would have happened by now. Making users do 
something special to get into a good configuration also violates Peter 
Gutmann's "Defend, Don't Ask"* rule. As a consequence, I'd like to move 
config.h to config.compat; and move config.recommend to config.h.

Any thoughts or objections?


* Also see Engineering 

You received this message because you are subscribed to the "Crypto++ Users" 
Google Group.
To unsubscribe, send an email to cryptopp-users-unsubscr...@googlegroups.com.
More information about Crypto++ and this group is available at 
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 cryptopp-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to