> The whole goal of switching to openssl is not to have to provide a > separate crypto library for linux builds, using a proprietary non free > implementation would be here the worst possible option. than I would just > stick to crypto++ as it already does all in needed. > Yeah, I agree. I feel like a lot of folks would benefit from ECIES if OpenSSL provided it. As a side benefit, people will want to avoid it in OpenSSL, so it will increase its usage in Crypto++, too :)
Related: http://security.stackexchange.com/q/86028/29925. Have you given any thought to how you would add it to OpenSSL's EVP interface? I've been thinking about talking to OpenSSL folks about it, like Matt Caswell, Richard Levitte and Emilia. 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.
