I’ve started writing interoperability tests (obviously data-wise only :) between Crypto++ and BouncyCastle (Java).
Looking at ECIES, I’ve stumbled upon a strange thing. Both http://en.wikipedia.org/wiki/Integrated_Encryption_Scheme and BouncyCastle define ECIES as a hybrid encryption scheme, and require use of both hash for MAC (i.e., SHA1) and symmetric cipher for the actual encryption (i.e., AES). Crypto++ however does not seem to use either hash or symmetric cipher at all. What gives? An old version incompatible with the current ECIES standard http://www.secg.org/download/aid-780/sec1-v2.pdf? Or am I missing anything? I’d appreciate any help and/or guidance. Thanks! -- -- 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/groups/opt_out.
