Hi Everyone, We went through the Visual Studio 2010 project files and cleaned them up. Its been an on-going cleanup, but there were three or four items this time. Also see "Visual Studio 2010 project file cleanup", https://github.com/weidai11/cryptopp/issues/314.
One of the necessary changes was the CRYPTDLL project, which the library uses when going through a validation. VS 2012 and above required us to opt-out of ASLR, while it allowed opt-in for VS 2010 and below. The change was committed so you not see the error due to relocations, "Crypto++ DLL in-memory integrity check failed. This may be caused by debug breakpoints or DLL relocation". For completeness, only the project can build the FIPS validated DLL. You can build a [crippled] DLL, but it won't be FIPS validated. Also see https://www.cryptopp.com/wiki/FIPS_DLL. If you want/need a DLL, then use the static lib - cryptlib.lib - as a starting point. Then, wrap the Crypto++ stuff you want in DLL functions which are exported by your module. Speaking from experience, its much easier that way. Jeff -- -- 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.
