On Friday, July 24, 2015 at 4:54:39 PM UTC-4, jean-pierre.muench wrote: > > Hey everyone, > > I've ran the build of our current GitHub hosted sources on my VS 2015 > installation and found the following warnings (build related, migration's a > different story) >
Can you send that to me or make it a PasteBin? > What I'll tackle tomorrow: > Try to apply the proposed fixes above, create up to 7 PRs for GitHub (up > to one for each change) and see what happens in the crazy DLL-Import builds > then. > My personal feelings: The DLL-Import stuff is hosed. Don't waste too much time or effort on it. Its hosed because that particular subproject was stood up just for a FIPS 140-validation. The Testing Lab required a Security Boundary due to an Implementation Guidance (IG) doc from the Cryptographic Module Validation Program (CMVP). The security boundary was created by the exported interfaces from the DLL. So the DLL export/import stuff was cut-in. That's also why things like HexEncoders are missing, and non-FIPS algorithms are missing. I'm not opposed to a DLL or even a FIPS DLL. We just need to take the time to re-architect it so the existing pain points go away. 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.
