Please test latest CMake changes
Hi Everyone, We added SM3, SM4, Simon and Speck recently. Changes were made to the Cmake files at https://github.com/noloader/cryptopp-cmake. Would someone please test them. Thanks, Jeff -- -- 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 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 cryptopp-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
New wiki page: Benchmarks
Hi Everyone, There's a new wiki page covering benchmarks at https://www.cryptopp.com/wiki/Benchmarks. It examines the benchmark process in detail, including how to set CPU scaling on Linux, how classes register their names and, how the library executes a benchmark including the overloaded functions based on the class' interface. Jeff -- -- 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 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 cryptopp-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: CryptoPP on Windows XP
Sorry, forgot to hit "Reply All" instead of Reply... Am 27.11.2017 09:55 schrieb "Marcel Raad" : Hi Mathijs, Am 27.11.2017 09:47 schrieb : To support a legacy product I had to build CryptoPP for Windows XP. However, the default behaviour in config.h causes some trouble with this. // If the user did not make a choice, then select CryptoNG if either // Visual Studio 2015 is available, or Windows 10 or above is available. #if !defined(USE_MS_CRYPTOAPI) && !defined(USE_MS_CNGAPI) # if (_MSC_VER >= 1900) || ((WINVER >= 0x0A00 /*_WIN32_WINNT_WIN10*/) || (_WIN32_WINNT >= 0x0A00 /*_WIN32_WINNT_WIN10*/)) # define USE_MS_CNGAPI # else # define USE_MS_CRYPTOAPI # endif #endif This means that when building with >= VS2015 but with XP as target, CryptoPP decides to start using MS_CNGAPI. This is available on the build system, but not on Windows XP, causing the application to abort on start. Of course this behaviour can be overridden by manually defining USE_MS_CRYPTOAPI or USE_MS_CNGAPI, but I think the default behaviour is not optimal. I don’t see why the version of VS matters in this check. this has been fixed in this commit: https://github.com/weidai11/cryptopp/commit/32f715f1d723e2bbb78b44fa9e167d a64214e2e6 Now only the target Windows version matters, not the Visual Studio version. Marcel -- -- 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 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 cryptopp-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: CryptoPP on Windows XP
On Monday, November 27, 2017 at 3:47:02 AM UTC-5, math...@thimeo.com wrote: > > Hi, > > To support a legacy product I had to build CryptoPP for Windows XP. > However, the default behaviour in config.h causes some trouble with this. > > // If the user did not make a choice, then select CryptoNG if either > // Visual Studio 2015 is available, or Windows 10 or above is available. > #if !defined(USE_MS_CRYPTOAPI) && !defined(USE_MS_CNGAPI) > # if (_MSC_VER >= 1900) || ((WINVER >= 0x0A00 /*_WIN32_WINNT_WIN10*/) || > (_WIN32_WINNT >= 0x0A00 /*_WIN32_WINNT_WIN10*/)) > # define USE_MS_CNGAPI > # else > # define USE_MS_CRYPTOAPI > # endif > #endif > > This means that when building with >= VS2015 but with XP as target, > CryptoPP decides to start using MS_CNGAPI. This is available on the build > system, but not on Windows XP, causing the application to abort on start. > Of course this behaviour can be overridden by manually defining > USE_MS_CRYPTOAPI or USE_MS_CNGAPI, but I think the default behaviour is not > optimal. I don’t see why the version of VS matters in this check. > Marcel will probably be able to answer better, but latter version of Windows and ARM builds Windows does not offer the CryptoAPI. They offer CryptoNG instead. Given that its 2017 we made the decision to favor what Microsoft is providing For Windows 8, Windows 10 and their mobile devices, and that's CryptoNG. To work around the problem, you should only need to define USE_MS_CRYPTOAPI. Then the library will fall back to legacy APIs. If you define it but still have problems with the wrong API, then that's a bug on our part. If you find your self in this situation, then please file a bug report. Be sure to state the platform details, compiler details, the command line you are using and the exact error message. Jeff -- -- 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 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 cryptopp-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
CryptoPP on Windows XP
Hi, To support a legacy product I had to build CryptoPP for Windows XP. However, the default behaviour in config.h causes some trouble with this. // If the user did not make a choice, then select CryptoNG if either // Visual Studio 2015 is available, or Windows 10 or above is available. #if !defined(USE_MS_CRYPTOAPI) && !defined(USE_MS_CNGAPI) # if (_MSC_VER >= 1900) || ((WINVER >= 0x0A00 /*_WIN32_WINNT_WIN10*/) || (_WIN32_WINNT >= 0x0A00 /*_WIN32_WINNT_WIN10*/)) # define USE_MS_CNGAPI # else # define USE_MS_CRYPTOAPI # endif #endif This means that when building with >= VS2015 but with XP as target, CryptoPP decides to start using MS_CNGAPI. This is available on the build system, but not on Windows XP, causing the application to abort on start. Of course this behaviour can be overridden by manually defining USE_MS_CRYPTOAPI or USE_MS_CNGAPI, but I think the default behaviour is not optimal. I don’t see why the version of VS matters in this check. Best, Mathijs -- -- 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 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 cryptopp-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
